What is the use case for Cygwin in the days of virtualbox/vmware?
Git
Gow – The lightweight alternative to Cygwin
21–30 of 95 posts
Re: Gow – The lightweight alternative to Cygwin
#22Re: Gow – The lightweight alternative to Cygwin
#23Oh, heretics! How dare they leave ed out of the list [1]? [1] https://github.com/bmatzelle/gow/wiki/executables_list
Re: Gow – The lightweight alternative to Cygwin
#24Earlier quoted context omitted.
That's available on Windows natively.
Really? I wasn't aware... since when?
Re: Gow – The lightweight alternative to Cygwin
#25Re: Gow – The lightweight alternative to Cygwin
#26We 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.
But when I think "Unix-like core plus package management on Windows"... well, Cygwin is already there.
Re: Gow – The lightweight alternative to Cygwin
#27What is the use case for Cygwin in the days of virtualbox/vmware?
(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
#28What is the use case for Cygwin in the days of virtualbox/vmware?
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
#29Re: Gow – The lightweight alternative to Cygwin
#30Earlier 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…
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.