PowerShell works on Linux today. It's consistent and works fine for this Go-developer's needs.
It's spectacular to have a shell with consistent verbiage and parameters.
It's spectacular to have a shell with consistent verbiage and parameters.
The problem is that it treats any output to stderr as an error and ignores actual posix errors (non-zero exit codes.) What's worse is in some contexts the error it throws on stderr is impossible to catch.
I really love Powershell in a lot of ways but this makes a lot of really basic scripts in bash very cumbersome to write in Powershell.
[Remoting Bug] https://github.com/PowerShell/PowerShell/issues/3996
[RFC for improved error handling] https://github.com/PowerShell/PowerShell-RFC/pull/88
Ultimately I just want Powershell to handle well-behaved posix apps in a sane way, but honestly the reaction of some of the people on the thread seems like there's a huge cultural gap between Microsoft and the Posix community. (Which, Microsoft claims to be a part of but clearly is not.)