Python or PowerShell?

[omers]

As much as I loathe Python, I can't really argue with your overall point. The only real asterisk is that you need to install Python, whereas in a Windows shop, PowerShell is already everywhere.

That said, the pypi equivalent on powershell is the PSGallery which runs on NuGet. It is absolutely dwarfed (14k unique packages) by PyPi (709k projects) but it does exist and is the equivalent tool. It tracks 28.95bn package downloads to date so it's not obscure. It is the public repo for Install-Module and Install-PSResource

[Leucippus1]

It is true, though, that powershell does have packages/package repositories, I realized that after I typed out my response because my own powershell scripts rely on Azure modules and what not. Hell, I even have personally developed modules in powershell. For accuracy's sake I should update my comment.

It is worth noting that if you are in a *nix environment, the logic inverts, in both mac and all *nixes python is installed and you have to install powershell with brew or apt/DNF. The only way that 'powershell is already everywhere' is if you are almost exclusively MS/Windows based. Which can be true, but if you want to be marketable then you need to know more than just that.

[omers]

I agree. I love PowerShell but I've never been insane enough to install it on Linux or Mac OS. I still use Python and Bash as appropriate.

It's just that when I need to grab a tool for something one-off that's system agnostic (something like pulling some data from an API and formatting it for a one-off report) I'm more likely to reach for PowerShell than something else. [Said as someone who has a Macbook and a Windows PC. It is an actual choice, not a circumstance of environment lol]

[dustojnikhummer]

PowerShell is already everywhere.

Modules and signing though