Probably, W2K is not a choice our newbie has made, but is a choice someone at his job made for him.
I think you are more on target suggesting Cygwin. I use W2K, because it's the best Windows OS, and I have to use Windows at work. But that doesn't mean that I'm not using Perl, running Emacs, using Cygwin, Ghostscript, serving web pages with Apache and mod_perl, etc, etc.
We monks keep repeating the mantra 'Use the right tool for the job' (and for good reason), and if you work in an office where you need to continually interact with other Windows users, pass Office documents back forth, or develop for the Windows platform, W2K becomes the best tool for the job.
<needlessly_poking_the_tiger>
when you say a Unix operating system, you mean MacOS X right? right? ;)
</needlessly_poking_the_tiger> | [reply] |
Yes Yes Right job for the tool ;)
But you must admit the CMD or command
are crummy command line interfaces
I have to use a NT box at work also
and thank God for Cygwin and their ports
of bash and Perl.
I bet you only use command or CMD to run
something like rxvt as I do.
And when I say Unix operating system I mean
a System V or BSD Unix OS.
I am not sure if OS X is BSD or System V like
but I am glad to see that Apple is getting into
developing good operating systems maybe someday
MircoSoft will do the same ... MSUnix? MSix?
I think that would be cool
Thanks for you feed back I enjoyed it! :)
--
Its like a dog that can sing and dance.
It's remarkable because it can do it.
Not that it can do it well.
P.S The above is what my CS professor said
to me after I told him that Windows started
supporting networking
| [reply] |