News for hackers. Stuff that matters.
Re:PowerShell Specification licensed under the Community Pro... by jkahn on Sunday May 08, 2011 @10:05PM (#2527271)
I agree snprbob86, and that's what I was getting at. PowerShell doesn't know if it's a shell or an object-based language.

It's far too verbose. It's a shell, and a huge pain to type interactively. Yes, it has tab completion, but so does bash - and that's far less verbose.

It's also opaque. Because it's object-based, but you work with it on the command line, it outputs in text but there is constantly "other" information that is not displayed on screen that you can get if you pipe through to another command. That's not intuitive. Text processing is intuitive.

It reeks of design by committee. It's own execution policy. Java-like getter/setters. Super verbose syntax. About the only good thing PowerShell has done is force Microsoft to provide a command-line, scriptable interface to all their server products to get away from GUI dependency. And that's a product of their PowerShell internal policy, not the language itself.

Yes, it's better than CMD.exe. But still a huge pain. Other platforms have Python, Ruby, Perl... and dare I say it, bash.

Re:PowerShell Specification licensed under the Community Pro... by contextfree on Sunday May 08, 2011 @10:30PM (#2527322)
Is it really all that verbose? The full cmdlet names like Get-ChildItem etc. are long, but there are standard abbreviations for most of them - which follow a more consistent naming pattern than short names in most languages/shells.
Re:PowerShell Specification licensed under the Community Pro... by shurane on Saturday May 21, 2011 @06:36AM (#2570625)
Is there a reason why Bash or *nix shells in general aren't popular on Windows?