Gow - The lightweight alternative to Cygwin
1–10 of 19 posts
Re: Gow - The lightweight alternative to Cygwin
#2Re: Gow - The lightweight alternative to Cygwin
#3Furthermore, the project is largely written in VBScript and batch files, which is insanity, even according to Microsoft themselves.
It was time to move to Powershell a long, long time ago. You even have solid projects like NuGet to jump off from for code and design. I can't take a project seriously when it's written in VBScript because so many of its constructs are shoddy.
But again, those last two paragraphs are meant as advice for living projects, which this one is not.
Re: Gow - The lightweight alternative to Cygwin
#4This is a junk submission. Where to start? This project hasn't shown activity in 10 months. Furthermore, the project is largely written in VBScript and batch files, which is insanity, even according to Microsoft themselves. It was time to move to Powershell a long, long time ago. You even have solid projects like NuGet to jump off from for code and design. I can't take a project seriously when it's written in VBScrip…
Re: Gow - The lightweight alternative to Cygwin
#5Re: Gow - The lightweight alternative to Cygwin
#6This is a junk submission. Where to start? This project hasn't shown activity in 10 months. Furthermore, the project is largely written in VBScript and batch files, which is insanity, even according to Microsoft themselves. It was time to move to Powershell a long, long time ago. You even have solid projects like NuGet to jump off from for code and design. I can't take a project seriously when it's written in VBScrip…
Re: Gow - The lightweight alternative to Cygwin
#7Re: Gow - The lightweight alternative to Cygwin
#8It's not a project that anyone else can reasonably use and build on -- it would be easier just to replicate the work. (Which I would like to do, incidentally.)
Re: Gow - The lightweight alternative to Cygwin
#9Re: Gow - The lightweight alternative to Cygwin
#10This is a junk submission. Where to start? This project hasn't shown activity in 10 months. Furthermore, the project is largely written in VBScript and batch files, which is insanity, even according to Microsoft themselves. It was time to move to Powershell a long, long time ago. You even have solid projects like NuGet to jump off from for code and design. I can't take a project seriously when it's written in VBScrip…
And, regarding batch files, if it gets the job done (i.e. M4 autoconf scripts). What would powershell give you?