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.
No UNIX Aficionado from my day ever had to leave emacs to do their work including their work on the side to define the meaning of life.
Oh, I’m sorry. Discussions of emacs are reserved for the religious forum. (LOL)
In python you can write shell scripts that are object oriented, use existing frameworks and roll your own objects/framework if you need to and can do it with or without a GUI ( ie. The Idiot Interface ).
There is about 4 or 5 other utilities with the same power in UNIX. They’ve been around for decades! Welcome to the party pal!