<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>shawxe</author><text>WSL filesystem performance is garbage, for one thing.  Chances are good that if you&amp;#x27;re using Windows but you want to be using a Unix OS, it&amp;#x27;s your work that&amp;#x27;s forcing you to use Windows.  And, if that&amp;#x27;s the case, chances are also good that the reason for that has something to do with a slew of legacy software that only runs on Windows.  If both of those things are the case and you&amp;#x27;re trying desperately to develop a Unixy workflow, very clean integration with native Windows binaries is an unfortunate must.  Cygwin delivers in that area much more effectively than WSL.  Obviously Unix is my preference, but if I can&amp;#x27;t have Unix than I&amp;#x27;d rather have Unix tools on the OS I&amp;#x27;m being forced to use than a Unix sandbox will always be less than a real Linux&amp;#x2F;BSD install but fails to integrate properly with the OS I&amp;#x27;m using by necessity.&lt;p&gt;The funny thing about both Cygwin and WSL is that, in my experience, many of the people who make use of them wish that they didn&amp;#x27;t have to make use of them. For me, Cygwin makes it a little easier for me to forget I&amp;#x27;m not where I want to be (especially with things like winpty and apt-cyg).  In Cygwin I can run URxvt just like at home, and run all the nonsense legacy software I need to for work, just like it were actually reasonable.  In WSL, I can do none of that.  It just doesn&amp;#x27;t work.  I have a few co-workers who run WSL alongside cmd.exe.  If I&amp;#x27;m going to have to do that, I&amp;#x27;d rather just stick to Cygwin.</text><parent_chain><item><author>neonscribe</author><text>What is the use case for Cygwin vs. WSL at this point?</text></item></parent_chain></comment><story><title>Cygwin 3.0.0-1</title><url>https://cygwin.com/ml/cygwin/2019-02/msg00229.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kazinator</author><text>Cygwin programs are (almost) native Windows programs. You can compile a POSIX-y program under Cygwin and it becomes a Windows program; you can ship it to a user if you just include a few DLL&amp;#x27;s that it needs.&lt;p&gt;I forked Cygwin&amp;#x27;s main DLL (cygwin1.dll) to create &amp;quot;Cygnal&amp;quot;: an drop-in alternative that provides more Windows-like behaviors in various areas. Programs built under Cygwin can be bundled with Cygnal. Then (for instance) they have path handling that is familiar to Windows users.</text><parent_chain><item><author>neonscribe</author><text>What is the use case for Cygwin vs. WSL at this point?</text></item></parent_chain></comment><story><title>Cygwin 3.0.0-1</title><url>https://cygwin.com/ml/cygwin/2019-02/msg00229.html</url></story>