3 ms·
This is why PowerShell rocks - superficially they're text pipes like any shell, but under the hood it's passing COM objects around. Nice.
by gaius 16y ago
This is why PowerShell rocks - superficially they're text pipes like any shell, but under the hood it's passing COM objects around. Nice.
- DrJokepu 16y agoActually, those are CLR (.NET) objects, not COM objects. Sorry for nitpicking.
- gaius 16y agoHeh, yep, old habits :-)
- CrLf 16y agoFor certain values of nice. While I find the PowerShell to be more powerful when I'm scripting stuff, I still prefer the unix shell mostly because it passes around and operates over text. Operating over text means you can compose a pipe progressively using what you see, without having to think about how it is structured internally. Operating over text makes the normal usage of the unix shell faster and more efficient than the PowerShell. That and the terser syntax. With the PowerShell I find myself always having to check the type of objects are being passed around and which attributes I should care about, while on unix I just "grep" and "awk" and I'm done. The PowerShell is more of a scripting language than a shell, while the unix shell is more of a shell than a scripting language. Although both of them are both those things.