3 ms·
Powershell passes data not instructions and a lot of those complaints sound like trying to write another language in Powershell. I've shoved json from node thro
by Already__Taken 2y ago
Powershell passes data not instructions and a lot of those complaints sound like trying to write another language in Powershell.
I've shoved json from node through Powershell into the clipboard and back to filter with select-object and out.
the situation making you invoke bat at all is what MS ruined and that's not Powershell fault.
- alganet 2y agoIt's not me deciding to mix bat and powershell, and it's not niche: https://github.com/search?q=powershell+language%3ABatchfile&type=code https://github.com/search?q=powershell+language%3ABatchfile&... There's a need for a fast, nimble glue that powershell can't deliver on its own.
- Already__Taken 2y agoThis is what I meant, these are all examples working around the default execution policy. That's microsoft ruining things not powershell as a language. I didn't say it was niche rare or wrong. It's just bad and it's MS's fault.
- lmz 2y agoTechnically it's Windows' "here's a string of the commandline, go parse it yourself" (vs. argv array) that's the issue as every program can interpret quoting, escaping etc. differently. All these programs being from MS (powershell, cmd) does make them a little guiltier I guess.