Care to explain that some? I've only poked around a little with PowerShell, but it freaking looks like it could do anything. It's modular, extensible, threaded, and has this huge library base.
I'm not defending -- I don't know that much about it except my initial impressions. Just curious as to why you would say that.
It can do anything in the same way that any other Turing complete programming language can, but that's not really enough.
As a shell, it's stuck in the same old Windows command line window that command prompt has always been, with all the problems that entails - no real resizing or decent mouse selection/copy and paste and so on.
As a shell, you want terse and concise hacking, it should be optimised for finger friendliness and oneliners that you aren't going to come back to. Powershell is not. It's wordy and verbose, C# style. It makes things complex because it's not easy to find what you're looking for. Object piping might be nice, but not when you have to get all files and pipe them into a get-modified-date thing and pipe the date objects into a date-to-text object instead of ls -...
As a programming language, it's seriously ugly. It could have been VBScript slid towards Python, instead it's C# slid towards Perl. See: http://blogs.msdn.com/powershell/archive/2008/10/18/emit-xml... from the official powershell blog from the main man behind powershell. $Ugh -*!
Care to explain that some? I've only poked around a little with PowerShell, but it freaking looks like it could do anything. It's modular, extensible, threaded, and has this huge library base.
I'm not defending -- I don't know that much about it except my initial impressions. Just curious as to why you would say that.