Re:Inside the Creation of the Microsoft Surface Book
by michaelmcmillan on Thursday October 08, 2015 @11:05AM
(#10353204)
That's actually the only reason holding me back as well. Cygwin is not very tempting.
[ Parent
| on HN ]
Re:Inside the Creation of the Microsoft Surface Book
by wvenable on Thursday October 08, 2015 @04:03PM
(#10355720)
Cygwin is terrible but there are alternatives, such as:
https://github.com/bmatzelle/gow
Which work extremely well. I can go back and forth between Debian and windows without too much trouble. Many tools are cross platform.
Re:Inside the Creation of the Microsoft Surface Book
by arm on Thursday October 08, 2015 @07:55PM
(#10357222)
How is Cygwin terrible exactly? It’s fast and lightweight (compared to other recommendations like MobaXterm) and has a huge selection of packages¹. Frankly, I don’t get why Cygwin gets so much flack; I’m glad it exists.
――――――
Re:Inside the Creation of the Microsoft Surface Book
by voltagex_ on Thursday October 08, 2015 @09:37PM
(#10357601)
Also msys2 which is well maintained.
Re:Inside the Creation of the Microsoft Surface Book
by tiedmann on Thursday October 08, 2015 @01:29PM
(#10354326)
And then there's vagrant. I switched back to MS because C# and profit, all other dev is on vagrant boxes which actually made things easier as I tend to be more comfortable with that what I push will work as I have the same *nix setup on my 127.0.01 as on remote.
Re:Inside the Creation of the Microsoft Surface Book
by michaelmcmillan on Thursday October 08, 2015 @01:43PM
(#10354448)
True, I had not thought of that. Any shortcomings?
Re:Inside the Creation of the Microsoft Surface Book
by joe5150 on Thursday October 08, 2015 @05:50PM
(#10356562)
Vagrant under VirtualBox is a little slow, but taking the time to set up WinNFSd is very worthwhile for real file I/O gains. If you want to pay for VMWare + VMWare's Vagrant plugin, you'll get even better performance.