bash in windows shellon bahWindows

I view this far more as a tacit admission on microsoft's part that they actually cannot be as good as bash or rsync or ssh.

If you couple this with microsoft's recent decision to use openbsd's openssh, coupled with a very large donation to the openbsd project to help fund this work and support the source of openssh, this could actually be microsoft throwing in the towel on shell tools. their powershell commands are so awkward and clunky compared to the mature shell tools of *nix that you really can't even compare the two.

I also was wondering at first about how they could possibly run any x driven tool, and the answer is, of course they can't, but they can run bash in a windows window.

The notion above in this thread that this would lose any linux desktop users is odd to put it mildly, this is just a shell, of great use to any dev environment with a lot of people running windows but interfacing with non windows systems via ssh, a good friend of mine works at one such large scale place, and I know they can use this directly as is, and probably will, because running all these emulators and putty's and other stuff just isn't as good as running native tools that hook right into the NT kernel.

So what this will simply do is let development environments where users already run windows for whatever reason now use better shell tools directly.

I don't believe the support will be anywhere near complete, for example, I doubt this will have the linux kernel core interfaces like /sys and maybe or maybe not /proc (though that's been emulated before on other platforms), so I just see this as getting the basics running so you can work in a real shell without indirect logic. bummer for stuff like cygwin and their project, but as with wine, I'm personally not a fan of emulators, I generally will just skip it, or run a vm if I need the feature. Apt on windows, lol, that's really funny though. Risky, because apt is so radically superior to any other package management system, particularly in the non existent version in the windows world, if anything, exposure to apt is very likely to push people to gnu/linux systems running apt.

Every time I run windows, I always wonder where apt is, then remember I have to do the download package, install, pray, thing, make sure to avoid 3rd party sources, all types of stuff, and I think if you show windows developers/admins these tools, after a while, you just get used to apt-get install, apt-cache search, etc, to install something you need, a little risky on Microsoft's part actually. I'm surprised the commenters in this thread haven't caught how significant apt on windows bash is, huge package pool by default.

Interesting development, for sure. I wonder if they have decided to forego internal openssh in powershell, or if they are going to go both ways, hard to say, powershell has a real userbase too, so maybe they are going for both, it's smart on their end.