Unless you are happy to spend your day in Visual Studio, in which case Cygwin will not be that useful.
Unless you are happy to spend your day in Visual Studio, in which case Cygwin will not be that useful.
All I really find missing these days is good line-editing, and a half-decent terminal emulator in which to run the shell.
Probably familiar enough for bash people:
https://github.com/lzybkr/PSReadLine
> and a half-decent terminal emulator in which to run the shell.
Not a terminal emulator (although I think it can do Terminal escape sequences if needed):
On Cygwin, try MinTTY. The default cmd.exe console is horrendous. This is derived from PuTTY and much, much nicer.
And, you can also find MinTTY standalone separate from the burden of cygwin. I got it from the msys project.
And that's the issue. Most people don't want to relearn everything, and I don't see why MS had to reinvent the wheel.
Everyone uses 7Zip now which has a very good command line version and is OSS/free (mostly LGPL licensed, but some of their source code is licenced otherwise because it is from third parties).
Plus Powershell can zip/unzip using the shell.application.Namespace API if you wish. I prefer 7zip myself, but Windows handles basic zip files fine.
I'd be surprised if compressor utilities running through Cygwin's emulation layer could achieve the same speed as a native tool. 7-zip is an open source tool that will handle all your compression / decompression needs on Windows (including rar, gz, many self-extracting exes, and a bunch of very exotic formats). You should really give it a try if you're compressing or decompressing large archives on Windows.
Why do you think so? The emulation layer should only be relevant for the IO part of the compressors and IO is usually severely limited by the harddisk anyway.
--edit apparently Bay Trail does support Linux. The big hype when it was launched was that it would not, that's where my confusion came in
the problem was the 32 bit UEFI. Also solved: http://unix.stackexchange.com/questions/155557/installing-li...
I'd be more inclined to agree with you if you'd ended that statement with "... designed for Unix, perhaps you should consider whether you should be using Windows in the first place".
There are a lot of people out there that have to use Windows for a variety of reasons, but are glad to be able to do some shell-related things on it in a unix-like shell.
At least for my stuff that will run in Linux (node/iojs and golang) targeting docker containers, it works well.