I have used pwsh in depth in the past. 4-5 years ago when I was exclusively Windows, doing SharePoint, AD, Azure, etc. Also local utility scripts. I have used

I have used pwsh in depth in the past. 4-5 years ago when I was exclusively Windows, doing SharePoint, AD, Azure, etc. Also local utility scripts. I have used bash in depth over the past year, I maintain the local dev cluster tooling at work (because nobody else wants to, see: bash). It's about 2kloc of pretty advanced bash. While PowerShell is a terrible language, piping around text (or rather, let's face it, JSON) is objectively worse. I do feel more productive with the Bash language/syntax, but I have no faith in any code that I write. Bash is littered with footguns and odd behavior. I have been learning nushell recently and have been greatly enjoying it. You get to pipe around structures, while avoiding the obnoxious PowerShell syntax. As an example from today, I was double-checking that some envars made it into a container image: skopeo inspect ... --format json | from json | each { |x| $x.Env } Now that's certainly possible with bash and jq, but I'd probably be leaning on Google even after 1000s of hours of maintaining a bash behemoth.