3 ms·
> Once you've piped strongly-typed objects around between your shell commands, text scraping seems barbaric by comparison This is why Powershell is a great thi
by mhurron 10y ago
> Once you've piped strongly-typed objects around between your shell commands, text scraping seems barbaric by comparison
This is why Powershell is a great thing on Windows. Windows works with .Net objects and Powershell works directly with those objects.
It's also why I don't see the reason to be excited that it can run on OS X and Linux now, because neither of those systems work by passing .Net objects around. You parse text with bash/sed/awk/perl/python ... because *NIX works on text based config files and commands that output text.
- ygra 10y ago> Windows works with .Net objects and Powershell works directly with those objects. I'd say COM, WMI, and the registry are more prominent parts of Windows itself than .NET is. However, PowerShell seamlessly works with those as well.
- jdmichal 10y agoI'm assuming that the Powershell port includes some subset of the standard cmdlets, which will handle serializing to and from objects.
- mhurron 10y agoA subset means it doesn't work as well or the same way.
- jdmichal 10y agoNo... It just means that all features may not be available. It makes no comments on how well the existing features work and how compatible they are with the Windows version. I mean, `Get-ComputerRestorePoint` and `Get-WmiObject` don't mean anything on Linux. I assume those won't be ported. `Get-Process` is certainly meaningful; I assume that will be. The ports might also have cmdlets not available on Windows. I could certainly see cmdlets to interact with `apt` in Ubuntu, or `yum` in RHEL. Especially since PowerShell is focused on provisioning and managing machines.