[fivesixzero]

As someone that grew up on bash the concepts that underlie PowerShell’s syntax are unnecessary reinventions at their best and utterly bizarre at their worst.

That’s the primary reason my hierarchy of Windows shells usually starts with bash (via WSL, MinGW, or Cygwin) for file management, ssh, compile/build/deploy, and text parsing work and ends at CMD and eventually PowerShell for the Windows services management and other Windows internals that require it.

Also, bash’s (and other similar shells’) high degree of customization is both easily portable and massively extensible. With some minor customization it’s possible to match, or even exceed, PowerShell’s tab completion capabilities.

[koala_man]

Do you have some examples?

I'm very familiar with Bash, but I've never used PowerShell. It doesn't seem like e.g. passing structured data would be a bad thing.

[contextfree]

As someone who's pretty familiar with both bash and PowerShell, I don't consider either of them better or worse than the other, just different. I think of PowerShell as something in between a traditional command-line shell like bash and a scripting language like python, with a mix of the strengths and weaknesses of both. It's not the best of both worlds, nor the worst of both worlds (each of which I've seen comments online arguing), it's just "some of the good and bad of both worlds."