3 ms·
Where does that happen for you? In my experience with PowerShell on Windows, you have to approach it more like interactive python with shortcuts rather than a
by munchbunny 7y ago
Where does that happen for you?
In my experience with PowerShell on Windows, you have to approach it more like interactive python with shortcuts rather than a regular shell, and once you’re accustomed it works fine. The main issue is that it doesn’t work like a classic shell, it just has some affordances to look like a classic shell in common use cases.
- danudey 7y agoAgreed; it's a lot more like a really weird iPython than it is a drop-in bourne shell replacement with quirks.
- emodendroket 7y agoIt's weird but once you get used to it I think it's cool. No more text munging!
- m0xte 7y agoWell it’s not the concept but the implementation that is at fault. From persistent random WinRM failures, sudden things breaking and the whole thing wrapping rancid bits of WMI and COM which leak through regularly, it’s just pain. On top of that the interface is somewhat flakey and slow. Plus some of the semantics feel like going back to circa 1995 Perl. Oh and don’t get me started on the nightmare that is script signing and security which really does nothing useful other than get in the way. It really feels immature. The biggest travesty is when it is integrated into something else such as ansible, packer, chocolatey etc where it will cost you a couple of days occasionally due to some obscure issue hidden behind even more layers.