[flukus]

Powershell has some good ideas, they just didn't come together as a whole. The idea of piping objects rather than lines of text might be good (I'm not convinced in either direction there) and probably much more efficient, but it's integration with .net hurt it. .Net code is just way to close to the "enterprise" spectrum of languages and way to terse for a shell. The powershell language itself inherits this lack of terseness.

When it launched there also wasn't a whole lot you could do with it, windows wasn't built to be automated by scripts like this. This hurt the uptake right of the bat and it never really reached that critical mass to become adopted.

A decade after powershells creation I still write batch files for windows specific things and stick to cygwin/bash for everything else. It's not even a familiarity thing, I learned (or at least tried to) powershell before I (properly) learned to use bash.

MS would have been better off creating language/environment independent binaries to manipulate windows.

> Not a sign of good product when you have to force it upon people.

This sums it up nicely, the only reason PS has any use whatsoever is because it has the MS name attached.

[mattmanser]

But it's hard to understand what you're saying as .Net's not a language, which one are you talking about?

I feel like I should stick up for C# as it's probably one of the best languages available today. I'm biased as I prefer statically typed languages so none of my brain is taken up by utterly useless information like having to remember the names of properties, methods, method signatures, etc. which the computer should bloody well tell me.

[e12e]

It might not be a language, but the .net object model/environment brings about as much joy to powershell scripting as the browser document object model brings to javascript...