4 ms·

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 pa

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. https://aka.ms/getps6-linux https://aka.ms/getps6-linux

lukeschlather 7y ago
The big problem with Powershell, and it makes it borderline unusable on Linux, is its crazy error handling. The equivalent of bash's `set -e` is `$ErrorActionPreference="Stop"`. 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.
- geekone 7y ago
  Do you have any examples of stderr errors being impossible to catch in PS, and/or a basic script that is very easy in Bash but cumbersome in PowerShell?
  - lukeschlather 7y ago
    Recently I was trying to automate something with gsutil (Google's storage CLI) using Powershell remoting to a Windows host. gsutil is a totally well-behaved posix app, which emits status information to stderr. The bug is specifically that when using remoting (Windows equivalent of ssh) the error is uncatchable. [Remoting Bug] https://github.com/PowerShell/PowerShell/issues/3996 https://github.com/PowerShell/PowerShell/issues/3996 [RFC for improved error handling] https://github.com/PowerShell/PowerShell-RFC/pull/88 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.)

lukeschlather 7y ago

The big problem with Powershell, and it makes it borderline unusable on Linux, is its crazy error handling. The equivalent of bash's `set -e` is `$ErrorActionPreference="Stop"`. 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.

geekone 7y ago
Do you have any examples of stderr errors being impossible to catch in PS, and/or a basic script that is very easy in Bash but cumbersome in PowerShell?
- lukeschlather 7y ago
  Recently I was trying to automate something with gsutil (Google's storage CLI) using Powershell remoting to a Windows host. gsutil is a totally well-behaved posix app, which emits status information to stderr. The bug is specifically that when using remoting (Windows equivalent of ssh) the error is uncatchable. [Remoting Bug] https://github.com/PowerShell/PowerShell/issues/3996 https://github.com/PowerShell/PowerShell/issues/3996 [RFC for improved error handling] https://github.com/PowerShell/PowerShell-RFC/pull/88 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.)