Nicholas Cain (6/23/2012)

---

Huge push for PowerShell and yet PASS completely screwed the pooch with the lack of PowerShell sessions at this years Summit with a precon, a spotlight and another regular session.

RBarryYoung (6/24/2012)

---

Agreed. I find Powershell to be surprisingly set-oriented for such a procedural/operational language. In many ways it's the most SQL-like language Microsoft has ever released to production. (besides actual SQL of course... )

peter-757102 (6/26/2012)

---

Not having worked with it, I did read some articles last year and was totally horrified by the language specifics and couldn't phantom somone getting language basics so wrong! A language needs to be precise and absolutely clear in its meaning, yes even scripting languages, but powershell code can be interpreted in many ways, most of them seem reasonable and useful in some situations, but only one is actually what it will do. That in itself constitutes a major fail I will argue here (I feel the same about perl for example)

I would absolutely HATE to be forced to use such languages, but for some reason some people adore cryptic and mystic languages and confuse them for powerful. I always seen this as soem sort of cult factor!

The mystic part will disapear if you know all the exact details and pay extreme attention to every letter, but at that point a scripting lanuage in my view already has failed!

chrisn-585491 (6/26/2012)

---

My main wish is that instead of creating YAPL (Yet Another Programming Language), Redmond could have leveraged a non-cryptic scripting language like Python. I enjoy learning, but the number of different language I need to accomplish my normal daily tasks is ridiculous!