2 ms·
This is the most common explanation, but tbh, it doesn't cut it: the consumer market runs on Windows 7/8, whereas PowerShell is most useful on Server 2008/2012;
by toyg 12y ago
This is the most common explanation, but tbh, it doesn't cut it: the consumer market runs on Windows 7/8, whereas PowerShell is most useful on Server 2008/2012; so why can't they enable it by default on the latter?
> A lot of medium to large enterprises have an internal CA (with the CA cert already on the machines for authenticating with AD)
That's not my experience, but I guess we're both going by anecdotes here. (to be precise, in the few cases where an internal CA is actually present, the process to have anything signed is usually a bureaucratic nightmare)
My particular point of view is a vendor who comes in to deploy stuff on customer servers and is told that Powershell should remain disabled (or be enabled for installation purposes and then disabled again, which removes the possibility of automated maintenance via PS). I guess it's a political choice as much as a technical one, but that's what I've experienced; and the larger the company, the most likely that this policy is not negotiable.
I don't disagree that PS has been successful; the Windows world was screaming for a half-decent shell and PS is exactly that. I just think that it could have been much more successful had MS chosen their defaults a bit more carefully (and/or implemented a better security model).
On the syntax, what I don't like is not being object-based -- I don't particularly like the "string everywhere" approach -- but rather the over-reliance on special characters (that tends to make a PS script fairly unreadable compared to Python). It also feels more of a bash-style world than a scripting-language world, which I think is a step back from VBS/JS.