There’s a reason why POSIX is still enduring to this day. Microsoft’s penchant for writing short novels for a basic command is not what I would call “better”. And that’s ignoring the fact that PowerShell doesn’t have a fraction of *nix shell capabilities and utilities.
Well, ya. Its terminal interface, I’d expect it to have “basic” capabilities.
also can run standard dotnet libraries.
That’s not exactly a selling point.
What can bash do that PowerShell can’t?
Write succinct and easy to read commands. Interop with all the powerful tools in the Linux ecosystem (which is the point of a shell like bash).
posix lost except insofar as it lives on in the two mainstream highly proprietary OSs.
That’s just simply not true. Three majority of core utils you find on most Linux systems are POSIX compliant or mostly compliant. IIRC all the GNU tools are POSIX.
It factually and objectively is not
There’s a reason why POSIX is still enduring to this day. Microsoft’s penchant for writing short novels for a basic command is not what I would call “better”. And that’s ignoring the fact that PowerShell doesn’t have a fraction of *nix shell capabilities and utilities.
Why is it factually and objectively not?
It has standard bash capabilities and also can run standard dotnet libraries. What can bash do that PowerShell can’t?
I’m skipping by the POSIX part because well…posix lost except insofar as it lives on in the two mainstream highly proprietary OSs.
Well, ya. Its terminal interface, I’d expect it to have “basic” capabilities.
That’s not exactly a selling point.
Write succinct and easy to read commands. Interop with all the powerful tools in the Linux ecosystem (which is the point of a shell like bash).
That’s just simply not true. Three majority of core utils you find on most Linux systems are POSIX compliant or mostly compliant. IIRC all the GNU tools are POSIX.
So your factual and objective point is, let me make sure I captured this right, is:
Cool