Does the world need yet another scripting language? I don't see anything particularly unique or compelling in PowerShell. It may be "cleaner" and more elegant than vb/ecma script, but that is because it is newer and has not had the need to accumulate the extensions and baggage of the others. Cmd.exe is sufficient for simple tasks and for more involved work I prefer to use something much less platform specific, Python.
I like Powershell in the fact that Microsoft really needed something like this for a long while. Bash is great. I just think its funny after all these years M$ is finally "starting" to take ques from others on how to go about doing things, I'll be it by adding their own little "touch" to it.
It's the OBJECT PIPELINE that raises PowerShell above the others.
You can do things in PowerShell with a fraction of the code it takes in VB, especially if you get in the habit of making your functions be pipeline functions. The scripting language itself is like only 15 keywords vs, VB's 130 or so. You don't need any more than the 15 key words, because of the power of accessing everything as an object, the power of the pipelining, and being able to access .NET objects. Also, anything you do in a script can be done in realtime in the shell... so you can test bits of code as you go.
It's actually superior to Bash scripting, IMO. It's Bash scripting on steroids (for Windows).
I love it being called bash. I don't why it's called that, probably for this reason.
all I can imagine is "... ... oh, come on ... what? why not?? COME THE F#&K ON! YOU ****ING ****! WHY won't you WORK!? ... ARGAFEWF@R$#2#$@#%! ... Oh thank God, Finally! there, was that good for you? you useless Piece of SHIT!"
to be fair I've never really used bash, but if cmd was called bash, that 'd be the reason.
Was this article really supposed to make someone want to use powershell? Je ne think-so pas. I see that in the time since I last examined it, powershell has become no less a fustercluck than it was then.
As for bash, its fans are those who have only been exposed to UNIX via Linux and its lamed-down hacked-up shells. bash is as sorry a substitute for ksh93 as Linux is for UNIX.
I think some are missing the point of PowerShell.
1. Its more then a shell, it has a language.
2. Windows needs it.
3. Like flairflan said above, "It's an OBJECT PIPELINE".
4. It was designed to work in the Windows world, thus very different requirements then *nix shells. For example, needs to talk to Objects without having to convert to text and back.
5. Used concepts from prior scripting languages, even Perl.
6. Built into latest Windows OS. So admin scripting is doable.
7. It's actually very expressive and easy to learn.
8. Good books on it already.
9. It is not perfect. What is?
How about a native 32-bit or 64-bit BASH shell with true redirection? I agree that powershell scripting is kind of cool, but if I were to replace cmd.exe I'd want to replace it with Cygwin BASH with xterm and fg/bg process switching.