Even better: In PowerShell, everything is an object va bash where everything is text. That means in PowerShell I can have a string of text like "Hello World" that acts just like a string does, but it also has all of the properties a string System.Object has, such as SubString, Length, Count, ToUpper, ToLower, etc.
When it first was introduced I was a bit 'meh' about it, but the more I used it and the more I understood it, the better and better it got. Now I can write scripts that used to be 60 lines of VBScript, or 30 Lines of Perl in only a few lines of PowerShell. I love it so.
@MiffTheFox said:
Powershell does have some advantages over bash, like not needing to call a text processing language for data processing. (Unless you think it's possible to do a task of nontrivial complexity in bash without sed, awk, or perl.)
You did neglect to mention TRWTF in PowerShell is that scripts by default have to be signed. At that point it's exactly as much work just to fire up Visual Studio and write a short C# or VB program.