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!
+1. I couldn't have said it better myself.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs