> Microsoft is building the most modern Terminal emulator
If it is anything like Powershell, which is more "modern" than bash, then I don't think it will make much of an impact. Powershell seems like it was designed by a comittee which did not quite understand the point of what they were doing.
It seems that if at least someone on that committee used a Unix terminal maybe once in their lives they would realize that what they were building would deliver a really bad user experience.
I read "Bad user experience" but I suspect what you mean is "It not what I am used to".
They (Microsoft) say that their inspiration was Korn Shell and Languages like TCL. Microsoft when they still offered Windows services for Unix, they did provide a Korn shell.
If you look at some PowerShell examples and some Korn Shell example there are quite a few similarities between the two.
So they obviously were quite aware of the options in the *nix world. I really wish people wouldn't make these sorts of claims when spending like less than a few minutes looking up the development history would dispel these ideas immediately.
Personally I really like PowerShell and I find it fun to program in whereas with bash I seem to have to always relearn it whenever I attempt to do something non-trivial. However I come from a background of programming in OOP languages like Java and C# so many it just suits my mental model better than bash.
In my (limited) powershell experience, it's a "scripting first" shell, while bash is more of a a cli-first shell.
Using a powershell cli is very verbose (although pretty consistent), but using it without some sort of GUI helper if you're not familiar with it is pretty daunting.
My assessment, from a history with a lot of bash and a little, not terribly recent PowerShell, is that PowerShell wound up in a pretty common position of having a better language but a worse UX. Picking out why (wrt UI in general, not powershell in particular) is an ongoing interest...
Not everything in Windows is a file so they created a shell based around pipeable objects and improved shell's logic handling. A bunch of terse commands for piping out text streams from files doesn't make a lot of sense here.
If it is anything like Powershell, which is more "modern" than bash, then I don't think it will make much of an impact. Powershell seems like it was designed by a comittee which did not quite understand the point of what they were doing.
It seems that if at least someone on that committee used a Unix terminal maybe once in their lives they would realize that what they were building would deliver a really bad user experience.