Maybe this is what the author uses cygwin for, but the rest of the ecosystem is really where cygwin has value if you want a unix-like experience on Windows. Also, why on earth would I want these es6 implementations anyways???
It’s not intended to replace cygwin, the title is misleading. The author doesn’t even mention replacing cygwin.
I like the idea and don’t care whether it’s written in ES6, PHP or Haskell. I haven’t touched a Microsoft OS in a few years, but if I had to I think I’d use something like this to quickly have a terminal I already know how to use. And switch to cygwin if I really need a heavier compatibility layer, not just a way to get around powershell without learning it.
es6 and node implies that this will work everywhere v8 and node is ported. Some components deployment and/or testing setup-teardown for testing integration with legacy components are still more easily addressed with shell scripts; for example simple lxc container orchestration where kubernetes is overkill. With this, as it cover more of the basics, your shell scripts will also run on windows, should running on windows be a requirement. Also, if you are using cygwin for heavy lifting on windows, I would suggest running a real linux distro in virtualbox to have full super-hero powers and not maintain 2 code bases. (I’m sure you know cygwin has quirks)
EDIT: my bad, replacing cygwin is not the primary aim of this project, but bash is mostly why I keep cygwin on my vm.