Live data from Hacker News

Gow – The lightweight alternative to Cygwin

github.com

21–30 of 95 posts

Re: Gow – The lightweight alternative to Cygwin

#26

We really need to port Homebrew to Windows so that projects like this can be the base, but people can pull in packages on top of it, like a lightweight Cygwin but more Windows'y.

pkgsrc already supports Windows Services for Unix, it may well work on top of this too (though I haven't looked at Gow yet and I honestly have no idea how it differs from MSYS).

But when I think "Unix-like core plus package management on Windows"... well, Cygwin is already there.

Re: Gow – The lightweight alternative to Cygwin

#27
post #5

What is the use case for Cygwin in the days of virtualbox/vmware?

I work at a company that currently provides a 32bit version of Windows 7 (the reasons are somewhat unclear.) But the bottom line is that we have the 3gb max addressable memory problem. When I have eclipse, outlook, chrome, various other dev tools and whatnot open, I'm often near the limit, and adding VMWare player or whatnot would probably be too much. So that's one reason... Plus, I find switching back and forth between a vm and the host OS still somewhat slow/clumsy.

(Yes, I know I should get a new job...)

I like the idea of Gow. Anyone know if you can achieve middle mouse button pasting as when you have X11 under cygwin?

Re: Gow – The lightweight alternative to Cygwin

#28
post #5

What is the use case for Cygwin in the days of virtualbox/vmware?

I'm a UNIX and Mac OS X transplant using Windows for embedded hardware development (almost all the tools are Windows-only).

I need a terminal from which I can operate on my Windows file system, but running an entire virtual machine is enormous performance-impacting overkill.

Re: Gow – The lightweight alternative to Cygwin

#30
post #18
post #15

Earlier quoted context omitted.

Does porting Homebrew make any more sense than porting something from Linux (for example)? My impression is that the Mac OS ones aren't as good. A package manager really sounds like the sort of project where the incompatibilities between *nix and Windows are large enough that writing a new one would make more sense. I think there are even existing projects like that for Windows; I remember seeing one on HN a while ba…

The advantage of Homebrew is that it is modern, small, and simple. Obviously apt is better, but apt also requires that you maintain a large repository of binaries. Homebrew is slow[1], but because it builds from source it is trivial to create a new package. Homebrew packages are just Ruby files. If the project uses Autotools, all you generally need to do is enter the URL, an md5, and the dependencies, then it Just Wo…

Everything you just said (packages are files, simple, uses existing tools for self update) applies to MacPorts too. The only real differences seem to be the use of Ruby, and an attempt to avoid replacing OS dependencies -- even if the replacements are newer.

In fact, MacPorts actually supports generating Debian packages and an apt repository straight from its port files.

As for Windows, Cygwin already provides binaries. An apt repository of them would be great. I'm not convinced porting homebrew or MacPorts makes sense, however -- they're both fairly Mac-focused.

Post reply on HN