[paulie_a]

Is there a chance this will be connected to a functional shell interface. I get your point that cmd cannot be upgraded because of legacy issues and that is understandable and unfortunate, but windows needs a proper shell. This is obviously a great start for one side of the equation. But until there is a decent terminal app, windows will continue to be a nonstarter.

[zadjii]

It sounds like you're asking for two different things here:

cmd.exe is a shell, and that's the guy that's parked.

conhost.exe is a terminal, and that's under active development, though it's slower than something like VsCode, because we can't just go adding features as we see fit, we have a LOT of back compat we still need to support.

Fortunately, conpty will allow for the creation of new terminal applications on Windows. If you're looking for a better shell experience on windows, I can point you to powershell or even [yori](http://www.malsmith.net/yori/), which looks pretty cool

[cryptonector]

I think u/paulie_a is just asking for a better shell. If cmd can't be made better, then make a new one.

[cwyers]

That's Powershell.

[paulie_a]

Exactly, I understand there are different underlying concepts and systems to the front end and what it interacts with. It just seem incredible that windows is basically stuck with a windows 95 interface for a shell.

[nailer]

Powershell is open source, the 6.1 preview 4 is nice and fast, and you get real objects with keys rather than scraping for regexs all the time like bash.

[AnIdiotOnTheNet]

Windows has a proper shell, it's called PowerShell and it is by far the most discoverable and consistent shell that exists.

[wtallis]

It's also the most absurdly verbose shell that exists, which means it sucks as a shell even if it's a half-decent scripting language.

[paulie_a]

I've attempted to use powershell numerous times, it's a piece of shit compared to zsh.