I switched my shell to pwsh a few years back when work had me doing heavy pwsh development. It worked, but… 1. It didn’t execute native commands directly, at l

I switched my shell to pwsh a few years back when work had me doing heavy pwsh development. It worked, but… 1. It didn’t execute native commands directly, at least then, so I was cobbling together pwsh functions to imitate ls, etc. 2. The pipeline is awesome, but incompatible with the default UNIX/style, where commands produce and expect text. Having said all of that, it worked and worked well, at least for my purposes (immersion and education). The pwsh pipeline is far more powerful, esp. since it passes objects and can maintain those: command B can perform work on the results of command A and C can access the results of both A and B with relative ease. The same trick is possible in bash, e.g., but requires some funky redirect and pipe management. One the pwsh work was done, I switched back to bash.