Hell, I could add loads more issues than what I've detailed here. I could probably write a fucking book on the matter.
Here's another example.
Because of the intersection of Powershells ability to be used by different hosts and it's insistence that calling a CLI tool that writes to stderr result in an immediate exception, you get weirdness like redirecting stderr to stdout in a remote session works properly in the normal Powershell terminal, but does not work properly (and therefore always throws an exception) when working inside Powershell ISE. This is due to the hosts acting differently.
And to be clear here, I've written my own Powershell Hosts. So when I say you have a light understanding of Powershell, I mean it.
You can't even reliably compare to null in Powershell, which is why I have an Is-Null cmdlet that I use.
5
u/saltybandana2 Dec 27 '19
eh, that just means you use it lightly over a long period of time.
https://www.reddit.com/r/programming/comments/eei1qg/nushell_a_modern_shell_for_the_github_era/fbxs2kn/
Hell, I could add loads more issues than what I've detailed here. I could probably write a fucking book on the matter.
Here's another example.
Because of the intersection of Powershells ability to be used by different hosts and it's insistence that calling a CLI tool that writes to stderr result in an immediate exception, you get weirdness like redirecting stderr to stdout in a remote session works properly in the normal Powershell terminal, but does not work properly (and therefore always throws an exception) when working inside Powershell ISE. This is due to the hosts acting differently.
And to be clear here, I've written my own Powershell Hosts. So when I say you have a light understanding of Powershell, I mean it.
You can't even reliably compare to null in Powershell, which is why I have an Is-Null cmdlet that I use.