This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Convince the Supervisor Time...


Sounds like you are using Microsoft products. 
If you consider NT, Win2k, VS, and batch files 
"up to the task of full scale production", your 
definition is sadly Microsoft-ized. Cygwin will 
work the same, if not better. Then there is the 
unbelievable advantage of being able to modify 
the source code to work correctly or specifically 
for the task. Did I mention that it is free?

HTH,
Peter

"Brian J. Ackermann" wrote:
> 
> Hello,
> 
> Myself and another co-worker have been interested in cygwin for quite some
> time now, and we've finally managed to convince our management to consider
> adding cygwin to our tool-set.
> 
> Basically, our situation would be the integration of various Visual Studio
> applications with perl applications and shell scripts.
> 
> Presently we are just using VS and batch files.
> 
> Our questions mostly are pointed at other developers/integrators who are
> doing similar things.
> 
> Is cygwin/[bash , perl] up to the task of full scale production.  Are there
> any memory leaks or other things that would prevent us from going where we
> desire?
> 
> Thanks for your consideration,
> 
> Brian J. Ackermann
> API
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]