By bloid
via weiqigao.com
Published: Mar 12 2008 / 22:13
I haven't used the A, B, C, ... style title for a while. Today's post calls attention to all distributors of Java products that provides a Windows batch file and a Unix shell script to run their product:
YOUR SHELL SCRIPT DOESN'T WORK FOR CYGWIN
Comments
joecoder replied ago:
Just use the windows batch file. Cygwin is a pain, especially when doing Java development.
weiqigao replied ago:
If you are a DOS BATCH file find of a guy, yeah, Cygwin is pain. But for a lot of people, it's the opposite---for them (me and people like me, I understand we are a minority), Cygwin is a pain, but DOS BATCH files are more pain.
joecoder replied ago:
Actually, I'm more of a Unix script guy. That's why I find Cygwin such a painful frankenstein environment for that supposed purpose. However, when I write software that will be used and potentially maintained by Windows developers, I'd lean towards writing DOS batch scripts (even if I'd need a long shower afterwards ;-)).
Voters For This Link (12)
Voters Against This Link (1)