[delta_p_delta_x]

Why not PowerShell, though? If you ever want to directly administer Windows through the command-line, PowerShell is increasingly your only bet, as older CMD executables are deprecated.

I'll suffix with my opinion that PowerShell is much nicer than many POSIX shells, especially given its hybrid object-oriented + functional pipeline paradigm.

[pixl97]

And following on this, for the longest time Windows only had extremely limited ability to manage itself via the command line and things were very haphazard on how you could manage them on the CLI. You were probably just using the CLI to edit the registry and restart serivces/executables at the best case.

This is really the reason there are no shells for windows. There wasn't anything for the shell to do! No massive collection of small executables linux *nix that were shell oriented. No system design around CLI management.

Around Windows 2016 or so I would say this changed with Powershell and with a number of design changes by Microsoft that allowed much better remote management (and not fully depending on GPO to do it), and I even run into some customers that have headless windows servers these days.