Former Windows admin and ex-HEAVY Powershell user here! I did too until I spent a few years using Bash and other programming languages. It's a super quirky lan

Former Windows admin and ex-HEAVY Powershell user here! I did too until I spent a few years using Bash and other programming languages. It's a super quirky language, and manipulating strings vs objects is a minor inconvenience, but I find Bash to be much more versatile in what it can do while being less verbose. I also like that it depends on other utilities for core functionality, as I'm a big believer of "do one thing, and do it well". Example: you can use Extract-Archive in Powershell (I think v7) to decompress ZIPs or tarballs (unsure if it works with gzipped archives), but what you can do with it is limited to the capabilities of .NET library and built-in shim from which that cmdlet originates. tar and zip/unzip, on the other hand, are classic coreutils that ONLY do this and, as a result, can handle many more edge cases, such as dealing with split archives. Anyway, I usually turn to a programming language if I find myself needing objects, as it's better suited for the task, and PoSh gets super complicated once you start invoking DLLs (IMO, though this opinion is 10 years out of date from back when PoSh 5 was new and Snover was still involved) Doubly anyway, PoSh is on Linux, as is .NET. It's usefulness there, however, is much more limited. For one, it isn't built-in like shells are. Additionally, because most *nix sysadmins will already know shell scripting, the motivation and need to learn it won't be as strong. In fact, the only time I've needed this was for some edge-case thing pertaining to Azure.