20 ms·
Gow – The lightweight alternative to Cygwin
- baq 12y agoi already have msysgit and mingw. should i use gow?
- rossy 12y agoProbably not. From the looks of it, GoW is just a mashup of MSYS and MinGW compiled binaries, much like msysGit except without Git.
- natch 12y ago>"Gow is one of the few things that makes Windows bearable/usable" Good quote, but that is not necessarily a positive if you look at things from the perspective of the sooner Windows is ditched, the better.
- blumkvist 12y ago2015 will be the year!
- quotemstr 12y agoWhy? Windows is an excellent system and gets a lot of things right that POSIX gets wrong. WMI is wonderful; COM is wonderful; the NT kernel is from 1989 and still worlds ahead of Unixy kernels in many respects. (It's 2014 and I still can't open a file descriptor that represents a process.)
- orf 12y agoI think some of your examples are iffy, COM and WMI are sometimes wonderful but sometimes definitely not. Windows is not perfect and POSIX is better for some use-cases, vice versa.
- quotemstr 12y agoOf course. The systems have a lot to learn from each other, to be honest. One of my biggest gripes back when I worked on the Windows team was the lack of a pseudoconsole API equivalent to the Unix pty interface. That said, using Cygwin is, as far as I'm concerned, the best of both worlds. Unlike some people, I like integrating the two environments as much as possible. I install Cygwin to C:\, for example, and I added support for using native win32 widgets to Cygwin Emacs. (Try the cyg32 package. You'll like it.) Try the "injob" utility too. It gives you native Unix job control with arbitrary Windows programs. (That it's even possible to implement it is a consequence of NT job objects being much better abstractions than POSIX process groups.)
- Sir_Cmpwn 12y agoThis doesn't really seem like an alternative to Cygwin. Cygwin is valuable because it provies a POSIX environment. I write my programs for sane systems and then Cygwin allows me to get them running on Windows fairly easily.
- justincormack 12y agoThe repo does not seem to have the source code, which is a bit of a problem as most of the software is GPL.
- jackalope 12y agoWhen I used to install Cygwin, it was to get (in order of importance): ssh, vim, rsync & X11. Gow doesn't include the last two, so it feels like an apples/oranges comparison (for my use case). Still, it's pretty amazing what Windows doesn't include by default in this day and age, so a simple, lightweight set of tools like this definitely has its place. I don't use Windows anymore, but if I did, I would probably just spin up a VM with a tiny live Linux ISO, because it would bring in so much other goodness without any extra effort.
- mikelward 12y agoIt only kind of has ssh. It has the PuTTY SSH client, but no SSH server.
- vertex-four 12y ago> Still, it's pretty amazing what Windows doesn't include by default in this day and age It includes the majority of stuff you'd want as part of Powershell, just under different names, and not available as separate executables on the filesystem. If Powershell is lacking something, you can access any .Net class on the system. Once OneGet is released with the next version of Windows and people start packaging stuff for it, you'll be able to grab additional utilities for pretty much anything. Windows isn't that far behind. It's mostly just not UNIX. Most things are there, just done in very different ways.
- pmoriarty 12y ago"Most things are there, just done in very different ways." Does it have something like the POSIX fork() system call? Apparently, its lack in Windows is the main thing that makes Cygwin as slow as it is.[1] [1] - http://stackoverflow.com/questions/2512892/how-to-speed-up-cygwin http://stackoverflow.com/questions/2512892/how-to-speed-up-c...
- pjmlp 12y agoOnly UNIX clones support fork() properly, because only UNIX clones processes. Any other non UNIX OS tends not to fully provide 100% fork() in they POSIX compatibility layer, or kind of fake it.
- deleted 12y ago[deleted]
- johnloeber 12y agoHonestly, I don't really understand why people use UNIX-shells like Cygwin in Windows. I found them slow and difficult to work with, to the extent that it's much easier to just spin up a VM with a lightweight Linux distribution (or to dual boot, but that's another use case).
- jamespo 12y agoProbably because they want something to work with their windows tools
- gfodor 12y agoYeah exactly, some of us are forced to develop software on windows (game development for example) so cygwin is a nice way to reduce some of the pain.
- roxtar 12y agoI develop on Windows for Windows and use these tools. Here is my reasoning. It's easy to see that Unix shell tools are much superior to the Windows cmd. There is PowerShell which gives you more flexibility, but in my experience I have found PowerShell to be slow. It also has a totally different set of syntactic rules which aren't worth my time to learn. Given that, I would rather install Cygwin or MinGW. Spinning up a VM is much more heavy-weight that just directly using Cygwin.
- quotemstr 12y agoPlus you can run nmake and cl.exe directly from Cygwin bash and everything works just fine.
- UnoriginalGuy 12y ago> There is PowerShell which gives you more flexibility, but in my experience I have found PowerShell to be slow. Powershell can be a little slow to launch. Actual execution speed is pretty respectable. It does get faster after the first couple of times as it will ngen stuff into the GAC (this is particularly bad on new Windows installs where little .Net code has previously ran in any contexts). It can be fixed by running a script like this: http://blogs.msdn.com/b/powershell/archive/2008/09/02/speeding-up-powershell-startup-updating-update-gac-ps1.aspx http://blogs.msdn.com/b/powershell/archive/2008/09/02/speedi... Which will populate the GAC. > It also has a totally different set of syntactic rules which aren't worth my time to learn. You're missing out. Powershell's syntax is quite intuitive after you learn the basics, you quickly start to be able to guess commands and params.
- bsenftner 12y agoLooking at the change_log, it does not look like their version of BASH has been updated recently, indicating it is capable of the ShellShock exploit.
- Elrac 12y agoThis seems hugely irrelevant to me. Would you consider using Unix lookalike utilities under Windows to launch an Internet-facing Web server that allows users to do CGI scripts? Because that's pretty much the only scenario where ShellShock would be an issue.
- quotemstr 12y agoCygwin is a fantastic system put together by people crazy and talented enough to dig deeply into both the POSIX world and the NT world. I can't recommend it highly enough. A bag of ported utilities is absolutely no substitute for something that, in effect, amounts to GNU/NT. Yes, there are some warts, but they're papered over remarkably well. Give mintty a shot: you'll never go back to conhost.
- diltonm 12y agoI completely agree, Cygwin has real OpenSSH, well you can even run Gnome on Windows if you want; even as your main shell or I was doing that back in 2002 not sure it would work these days. Overall Cygwin can't be beat. If Gow has enough utility for folks who want to use it; that's cool but for me when I'm stuck using Windows for anything, Cygwin rocks.
- a3n 12y agoI run cygwin X so that I can have the tabbed version of urxvt.
- fuzzix 12y agoI ditched mrxvt long ago because of lack of Unicode support (though I did use it under Cygwin/X). https://github.com/simonzack/urxvt-tabbed https://github.com/simonzack/urxvt-tabbed - is this the project you're using?
- a3n 12y agoNo, not an external project, just one of the "official" rxvt variants. I use the same one on linux as on cygwin/X. rxvt-unicode-256color I use it on cygwin at work because I use it on linux at home, because of the tabs (which are text-based and have nothing to do with whatever desktop environment it's running in), and because the 256 colors make it easier for me to distinguish different code parts in a colored text editing session. The default terminal in cygwin is OK, but the small number of colors were really bothering me (old eyes). As for unicode, I've displayed Japanese and other scripts in rxvt-unicode-256color just fine.
- deng 12y agoFrom the looks of it this is definitely not an alternative to Cygwin, because the latter implements a complete POSIX layer. Instead, this seems to be a collection of native and MSYS binaries, which is fine and all, but I kinda doubt that they have the quality of ezwinports, which is still the best address for native Windows binaries of free software. Also, they don't provide the source and the build scripts for their binaries.
- GilbertErik 12y agoYeah yeah. I opened this: https://github.com/bmatzelle/gow/issues/164 https://github.com/bmatzelle/gow/issues/164 Please comment with clarifications.
- xfGnB6P 12y agoI gave Gow a shot when I got a new Windows PC at work a while back. In my experience it is completely broken for anything but the most trivial use cases. Basic things didn't work, like "ls -t|head" (broken/missing SIGPIPE implementation IIRC), and "(g)find -iname '*.txt'" (I could not for the life of me stop it from expanding the glob). I gave up after a couple days and went back to cygwin.
- mlvljr 12y agoWas my experience with Cygwion itself 9 years ago or so -- broken beyond usable for anything except look-ma tests :)
- lnanek2 12y agoThis doesn't seem to have some of the things I use in Cygwin, so it useless to me. Also 10MB vs. 100MB is irrelevant to me. I don't download any movies and music or anything like that so my tiny flash hard drives still have plenty of room to make that difference irrelevant. Might be good for some people.
- jedisct1 12y agoWhat's the point over MSYS2?
- UnoriginalGuy 12y ago> Shell window from any directory: Adds a Windows Explorer shell window (screenshot) so that you can right-click on any directory and open a command (cmd.exe) window from that directory. Windows already has that, hold down shift and right click either on a subfolder or in the white space/nothing within an open folder. Since, I dunno, XP maybe? I don't think 2000 had it. I know Vista did.
- fencepost 12y agoThat was almost certainly the "Command Prompt Here" powertoy for XP, but it was then integrated into Vista and 7.
- vram22 12y agoYes, it was probably that. Some of those powertoys were cool. I remember installing and using that one. Didn't know that it was integrated into Windows 7 with that Shift+Right-Click shortcut though, thanks.
- pjc50 12y agoWell, that's kind of undiscoverable; it really ought to be on the shell extension context menu.
- UnoriginalGuy 12y agoMuch like Mac, Windows is designed for consumers primarily, power users/programmers/etc secondarily. It can be reconfigured to appear without shift: http://superuser.com/questions/240279/windows-open-command-prompt-window-without-holding-shift http://superuser.com/questions/240279/windows-open-command-p... Although the Windows 8.1 right click bottom left for the new Power Users Menu was a welcomed addition that consumers could inadvertently run across.
- gentlebend 12y agoWhile we're on the topic, here's a cute tip: To make the opposite move -- from the command prompt to an explorer window of the current directory -- use "start ."
- tonyplee 12y agoHas any tried busybox for Windows? How is that compare to Gow?
- jhallenworld 12y agoThey should provide tools that run in both Windows and plain MS-DOS / FreeDOS (hey, sometimes it's useful). One way I know how to do this is to compile with http://www.delorie.com/djgpp/ http://www.delorie.com/djgpp/ and link in the CWSDPMI DOS extender from http://homer.rice.edu/~sandmann/cwsdpmi/index.html http://homer.rice.edu/~sandmann/cwsdpmi/index.html The DOS extender will not run if it detects DPMI provided by Windows, so the binaries work in both environments. I suggest this for some Atari 800 utilities I wrote: https://github.com/jhallen/atari-tools https://github.com/jhallen/atari-tools
- lolive 12y agoI dunno about Gow. But I have been very happy with the (not so) small package included in MobaXterm: ssh, X11, busybox, git, perl, ... http://mobaxterm.mobatek.net/ http://mobaxterm.mobatek.net/
- callesgg 12y agoUnfortianly Gow is very buggy. And the maintaner does not reveal sources for the binaries, which makes it hard to help out. In practise he is acctualy breaking the GPL license, by not giving sources.
- vram22 12y agoI had used UWIN for a while a few years ago, when I was on Windows and needed UNIX functionality: http://en.wikipedia.org/wiki/UWIN http://en.wikipedia.org/wiki/UWIN It was originally written by David Korn, creator of the Korn shell. Can't forget "ksh -o vi", which let you edit your command history with vi commands. (It is like "set -o vi" on bash these days.) I used to use it as the last line in my .kshrc. http://en.wikipedia.org/wiki/David_Korn_(computer_scientist) http://en.wikipedia.org/wiki/David_Korn_(computer_scientist) Not sure where UWIN stands in comparison to Gow and Cygwin but it was somewhat useful. IIRC, it was at least more than a collection of UNIX utilities. The installation procedure (from an AT&T site) was a bit of a pain but doable.
- geofft 12y agoI like how we live in a world where you can say "open source" and put a bunch of compiled binaries in a bin directory. Leaving aside the trail of GPL violations, it's ... certainly something ... that the phrase "open source" doesn't make people think about whether source should be _present_, open or otherwise. The "contributing" page is pretty awesome, along the same lines: it describes a list of things you need to do in order to ask the maintainer to implement the feature you want.
- kolev 12y agoI've been using Babun [1] and fully enjoying it. [1] https://babun.github.io/ https://babun.github.io/
- Demiurge 12y agoI still use Windows SUA for my unix needs on Windows. It allows me to do most things and provides real POSIX (except fork), but stuff like sensitive filenames and unix style permissions actually work with NTFS. OpenSSH runs as a real service, and so on. I don't understand why this subsystem never got much recognition and suacommunity.com is even dead now...
- pjmlp 12y agoOriginally Windows had the concept of personalities and three were available Win32, OS/2 and POSIX. OS/2 went away, as soon as, OS/2 stopped being relevant. POSIX was there mostly to get the foot into the door of US government, due to its requirements in POSIX compatibility. I guess when this stopped being required and Win32 was accepted as viable platform, there wasn't a business case to keep on spending resources in POSIX support. After all, Windows is not alone in lack of full POSIX support when one looks to embedded and mainframe OS as well.
- bdunbar 12y agoI've read about Windows SUA (and it's predecessors) but have never been sure what problem it solves for me. Got a use case or two?
- nstart 12y agoI use cygwin on a daily basis and the only question I have is, apart from a smaller disk space footprint, which is becoming increasingly relevant, how much more lightweight does one need cygwin to be? This obviously does not apply to the true power users of cygwin. I was thinking more along the lines of a general user of it. Basic greps, batch file operations, etc.
- devniel 12y agoI have been using Gow almost three years, it's a great tool !