Color me unimpressed. Powershell was never more than a strained imitation of Unix shell scripting and still does not have the power. Got some handy wrinkles, though. I wouldn’t give it up but is certainly isn’t the Holy Grail.
Color me unimpressed. Powershell was never more than a strained imitation of Unix shell scripting and still does not have the power. Got some handy wrinkles, though. I wouldn’t give it up but is certainly isn’t the Holy Grail.I think PowerShell is greatly superior to the classical Unix shell. In PowerShell, you have real objects with properties and methods going through the command pipeline. In the Unix shell, all you have is an unformatted stream of octets, which you then have to parse again and again with crude tools like (f|e)grep, sed and/or awk to get at the information you want.
ps | where { $_.ProcessName -eq "hexchat" } | select WS
is just better than having to grep the ASCII output of "ps", then using awk to get at the column value for the memory usage.
(Of course, PowerShell's ps command even supports giving it the process name as an Argument, as in "ps hexchat").
What’s more, you have the entire .NET Framework available in your scripts, plus various remoting capabilities, etc. The Unix shell still feels like it’s 1975 again in comparison.