Re: PowerShell
"The way I had it explained to me: PowerShell made sense because it was an easy and familiar approach for the squillions of extant .net programmers that existed.
Also: the APIs exist independent of PowerShell. Nothing is holding anyone back from extending another scripting language to do the same thing, if they like it better. If you are willing to make a serious attempt, I am almost positive Microsoft will not only welcome it, but probably devote resources to help."
Yes, you like MS and Windows. It is the only solution for you, WE GET IT. I'm in a hederogeneus enviroment. I have Linux, Solaris, BSD, MacOS, Windows (server and desktop), and ESXi; best tool for the job, wouldn't have it any other way.
"Don’t assume malice here; Microsoft have a strong business case for openness. They are making a cloud play. Public and private. That means making sure that their software can be managed and addressed by as many people as possible. .net made sense to start with – it was the community that already existed around their products. Thus PowerShell made sense."
I never assumed malice. I assumed ANOTHER case of NIH-syndrome, but now that you mention it, MS's busness case is for getting users onto their platform and keeping them there. Promoting skills which are useful outside of their platform is not something which, long term, is useful for them.
I've used it, It's an okay scripting language, BUT I can see no compelling advantage to useing it over any number of other languages, except MS has taken care of the API-bindings for me (that IS a compelling reason to use it (in the windows enviroment), but not enough to justify it's existance). It also means I CANNOT reuse ANY code from other platforms, nor as effecently use my existing staff.
Later on...
"My time is worth money. The time of my staff are worth money. If you save me so much time by making you product easy to use that you offset the cost of "proprietary," then there is a damned good reason to buy that product."
Funny, that's EXACTLY the reason why writing an entirely new scripting language to expose these features makes no sense. MS isn't looking after me with this, they are trying to get me to aquire a MS-excluseive skill. I'll admit, It did work, although I am still nowhere near as fast in PS then in any number of other scripting languages.
"An open standard/language/interface/source code/whatever that can only be understood after having 50 years of theory injected directly into your eyeball then jacking into the matrix whilst whistling the Dr. Who theme in exactly the right pitch is completely useless."
I've yet to encounter more then a handful of scripting languages which fall under this, and I wouldn't advocate them for wide-spread usage. Noone here is, as far as I can tell. Ergo, this is a non-sequitor.
"Whereas an application that costs me $750, takes 5 minutes to set up, and just works for the next ten years pays for itself in no time."
PLEASE call me when MS provides this in the virtualization space. PLEASE, PLEASE, PLEASE. I have been hearing MS claim to be the best platform for vitrtualization since they where trying to bribe us with 1USD chips at VMWorld '08. The weren't then. They may be getting more useable, but I'm not yet convenced. As it stands, the last time I needed a fix because MS screwed something up, the responce I got from support (at my cost, both monitarily and a couple weeks of my time, mind you) was: Yep that's a bug. The fix will require massive disruption to you're entire user-base with and hundreds of man-hours of downtime for your userbase to fix.