This 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 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.
Giving the guy a break, it does look like he doesn't "get" github, as it hosts the sources(not in an easily buildable format) as a binary download. and the content of the repo is just random batch files.
And, regarding batch files, if it gets the job done (i.e. M4 autoconf scripts). What would powershell give you?
I've never submitted Gow to Hacker News but it does seem to pop up every once and a while and it gets the project a few hits.
This is a project I work on in my free time (and I get paid very well hourly so it's expensive to me) and if it weren't for programmers like me you wouldn't be able to do half the things you can do on your computer, so unless you've spent thousands of hours coding for free then please stop spreading the hate.
> This project hasn't shown activity in 10 months.
Please do your research. I just made a big release yesterday so the user that posted this wasn't just spamming HN.
> Furthermore, the project is largely written in VBScript and batch files, which is insanity
I wrote that script 10 years ago and it works with every version of Windows from Windows 2000 on. I made Gow so I could use Unix utilities on all versions of Windows. If I wrote it in PowerShell then it would force all users to either use a new version of Windows or download the PowerShell installer for zero added benefit. The script just adds Gow\bin to the PATH. Gow certainly doesn't need PowerShell for that.
> It was time to move to Powershell a long, long time ago.
Except Powershell uses a wholly different paradigm, won't run people's favorite shell scripts they've carried around with them for decades, and makes people's ingrained years of experience and learning largely moot. That doesn't sound like much of a "win" to me.
Gow, mingw, cygwin solves a very large need for very many people, for which Powershell is 100% inadequate.
The bigger purpose of cygwin is to be able to compile your unix c/c++ to run on Windows. The shell utils is a small part of it, and better covered by things like UnxUtils and the various sets of binaries of the actual unix shell utils that people have packaged already.
Apparently, since last time I looked, there's actually source code. It's a tarball containing a collection of zip files of different layouts, with no documentation of how to actually build things, some build trees, etc. Many of the packages in that tarball are years out of date.
It'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.)
GOW seems to be more focused on a userland environment, whereas mingw is focused on enabling developers to link against unix libraries in a windows environment. Sure there's msggrep, and msgfilter as userland in mingw, but GOW gives you direct access to 'ls', 'gfind', 'grep', etc, and doesn't care a fig about giving access to libz.
My only problem with Cygwin is that installing and updating packages is a pain since you need to use the setup program. Apart from that it works great for what I use it for - a unixy shell with ports of a few tools I like using.
I have been using this package for months and I'm happy with it. My setup includes console2 + mingw (git for windows) + gow and it meets my expectations. I don't care if it's written in VBScript as long as it works. I have OSX at home and I can always use a Linux box if I need something more.
I'm glad that this post actually pointed me to the brand new release which hopefully will provide a fix for a file permission bug that I recently hit.
UnxUtils is another similar package that I have successfully used in the past. I think I jumped to Gow because I saw it here by the time I was getting back to Windows.
Personally, I think Gow is awesome. The few times that I need power unix stuff, it's been just there, and it just works. That's the most important thing.
For me, it's worth the 'price' of admission, just to get a usable instance of 'gfind', and avoiding the cognitive dissonance of typing 'ls' and not getting useful info.
18 comments
[ 3.2 ms ] story [ 49.2 ms ] threadFurthermore, 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.
And, regarding batch files, if it gets the job done (i.e. M4 autoconf scripts). What would powershell give you?
> This is a junk submission. Where to start?
I've never submitted Gow to Hacker News but it does seem to pop up every once and a while and it gets the project a few hits.
This is a project I work on in my free time (and I get paid very well hourly so it's expensive to me) and if it weren't for programmers like me you wouldn't be able to do half the things you can do on your computer, so unless you've spent thousands of hours coding for free then please stop spreading the hate.
> This project hasn't shown activity in 10 months.
Please do your research. I just made a big release yesterday so the user that posted this wasn't just spamming HN.
https://github.com/bmatzelle/gow/wiki/change_log
> Furthermore, the project is largely written in VBScript and batch files, which is insanity
I wrote that script 10 years ago and it works with every version of Windows from Windows 2000 on. I made Gow so I could use Unix utilities on all versions of Windows. If I wrote it in PowerShell then it would force all users to either use a new version of Windows or download the PowerShell installer for zero added benefit. The script just adds Gow\bin to the PATH. Gow certainly doesn't need PowerShell for that.
Except Powershell uses a wholly different paradigm, won't run people's favorite shell scripts they've carried around with them for decades, and makes people's ingrained years of experience and learning largely moot. That doesn't sound like much of a "win" to me.
Gow, mingw, cygwin solves a very large need for very many people, for which Powershell is 100% inadequate.
It'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.)
http://code.google.com/p/apt-cyg/
I'm glad that this post actually pointed me to the brand new release which hopefully will provide a fix for a file permission bug that I recently hit.
UnxUtils is another similar package that I have successfully used in the past. I think I jumped to Gow because I saw it here by the time I was getting back to Windows.
For me, it's worth the 'price' of admission, just to get a usable instance of 'gfind', and avoiding the cognitive dissonance of typing 'ls' and not getting useful info.
And it's not the PITA that is cygwin.