On the topic of Powershell on Linux I think the story there could be different, however Powershell violates the core philosophy of Linux so hard (mit vs. GPL, pipe-and-filter vs loaded DLLs, ...) that Powershell will never be something integral and natural fitting there.

> mit vs. GPL

By this measure, we shouldn't be using X or Wayland because they're MIT.

> pipe-and-filter vs loaded DLLs

At first I didn't understand what you were referring to, but I realized you were talking about cmdlets. In that regard, PowerShell is more like a scripting language than it is like a traditional Unix shell.

The more "Unix-like" approach would be to write thin command-line wrappers around the libraries you want to use. If I'm not mistaken, this is how projects like LAME and FFmpeg are implemented.

Regards the licencing: you are right. I was a vit blinded by the core gnu tools.

Tiny wrappers do not work since .NET, while being very Performanz will never be C like tiny.

> Tiny wrappers do not work since .NET, while being very Performanz will never be C like tiny.

I meant tiny wrappers around non-.NET libraries, to approximate the functionality you get in PowerShell in a traditional UNIX shell.

WSL2 availability makes powershell redundant for most server oriented dev tasks.

Translation: WSL2 makes running traditional tools for managing *nix servers easier from a Windows machine.

Dev tasks. Yes. Admin tasks: not so much. The ask is not to create a windows client env to administer Linux machine. The ask is one management surface for Linux and Windows servers.