7 ms·
I wonder if the new Linux compatibility subsystem for Windows provided any motivation for this change? That work seems likely to make Cygwin obsolete eventuall
by JoshTriplett 10y ago
I wonder if the new Linux compatibility subsystem for Windows provided any motivation for this change? That work seems likely to make Cygwin obsolete eventually, since it allows running unmodified applications rather than porting them.
- rcarmo 10y agoI'm going to oversimplify a bit, but unmodified applications cannot have a native GUI or break out of the Linux Subsystem sandbox (other than network connections). You can cheat using VNC to localhost, of course ;) I have it installed, and still rely on Cygwin for projects that live on my Windows directory.
- digi_owl 10y agoOr run a xserver on Windows.
- throwanem 10y agoSuch as Cygwin/X, available from a friendly cygwin.com near you!
- daurnimator 10y agoComing soon: http://midipix.org http://midipix.org
- richardfontana 10y agoNo, this change was being contemplated over a year ago and the final internal decision was made before the announcement of that Linux compatibility subsystem. It has more to do with the commercial viability of Cygwin as a product.
- namtrac 10y agoI sincerely hope Red Hat continues to develop Cygwin further. It's amazing to be able to run my favourite shell on Windows.
- ktRolster 10y agoI'm guessing it was because of pressure from Mingw. A few years ago, Cygwin was the only option, and Mingw was a real pain to use. Now with Mingw becoming more and more mature, I'll bet people were using that instead of Cygwin.
- xorblurb 10y agoCygwin and Mingw are not really comparable. And if you are thinking about MSys, it's a fork of Cygwin, so...
- kazinator 10y agoMSYS is an ancient branch of a common code base with Cygwin, which only needs just enough POSIX content in order to compile the utilities which are included in the toolchain which MSYS supports: the toolchain known as MinGW. That toolchain itself doesn't link programs against MSYS; it links programs against Microsoft's redistributable C run-time library (MSVCRT.DLL). Essentially, MinGW is a cross-compiler. MSYS is a kind of "non-user-serviceable area" that you wouldn't deal with unless you were hacking on MinGW itself. Say you wanted to add some missing utility to MinGW, and there was some issue between MSYS and that utility requiring MSYS hacking. If you think that you have a POSIX program that could benefit from being linked against MSYS, you're almost certainly better off just using Cygwin to port it. And now you can redistribute the Cygwin DLL with that program without tainting the program with the GPL.
- geofft 10y agoOne big difference between Cygwin and the Linux subsystem is that Cygwin runs Win32 processes, under the Win32 subsystem, so the entire Windows API is available to you. The Linux subsystem (like the Subsystem for UNIX Applications before it) is a separate set of concepts on top of the raw NT system calls, so you get a GNU/Linuxish API instead of the Windows API. With Cygwin you get a GNU/Linuxish API as well as the Windows API. See, for instance, this discussion about how copy-on-write fork is available as a system call (and had been around for a while, to support SUA), but doesn't work right with the Win32 subsystem, and that means Cygwin can't use it: https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/afdf1b68-1f3e-47f5-94cf-51e397afe073/cygwin-fork-and-rtlcloneuserprocess?forum=windowsgeneraldevelopmentissues https://social.msdn.microsoft.com/Forums/windowsdesktop/en-U... I don't know how many actual applications take advantage of this, though. But if they do, then Cygwin is definitely not obsolete for them.
- JonathonW 10y agoThe Linux subsystem also runs unmodified Linux binaries-- with WSL, you can (theoretically) run any piece of software compiled for 64-bit Linux, which gives you access to everything in Ubuntu's package manager (Ubuntu's the only distro they ship right now). With Cygwin, programs have to be recompiled for Cygwin, which means you're restricted to programs that are either already in Cygwin's package manager or that you can compile yourself. As you mention, WSL also isn't stuck with the restrictions that come from Win32 compatibility. One of the big impacts of this is that fork() can be faster (although I'm not sure if it actually is right now) than the mess that is Cygwin's emulated fork(). There are some more subtle distinctions, too, though: for example, WSL maintains Linux's conventions around locking open files and has full case-sensitivity. Cygwin doesn't even try to simulate Linux's behavior for either of those; it maintains Win32's behavior.
- Sir_Substance 10y ago>With Cygwin you get a GNU/Linuxish API as well as the Windows API. Genuine question, why is that useful? Intuitively, it seems like if you ever used that capability, you'd end up with a horrible chimera program that can't run on linux or windows, which doesn't seem good.
- skrowl 10y agoOne thing that I didn't see mentioned here that I'd like to point out (again) is that the Ubuntu on Windows stuff is CLIENT ONLY aimed at developers. Microsoft has said that they have no plans to push it to / support it on their Server OSs. If you're planning on SERVING something with Windows + Linuxy stuff on top of it, Ubuntu on Windows is not an option.