I admit that my perspective on it is very much that of an administrative script-bodger, so most of the elegance is lost on me; but the thoroughness with which the bits of of Windows that need twiddling have been exposed in Powershell for twiddling is highly appreciated.
On a theoretical basis, I can appreciate the virtues of the fact that MS has gone from having pretty much the lousiest scripting environment available to having a shell heavily anchored in its (mostly well received) software development tools; but I’m too much of a lightweight for that to really change how I use it very much. This hardly means that “your shell scripts can seamlessly range from basic batch files up to basically full .NET development” is a bad thing; it’s just not a thing that I’m enough of a developer to make any use of.
The fact that Microsoft is taking a fairly serious stab this time around at making “If you can do it in the GUI, you can script it, period; plus you can script a whole bunch of other stuff.” actually true, by contrast, is something that has saved me considerable weeping and gnashing of teeth. If I sucked less at programming the elegance of the implementation would probably matter more to me; but since I don’t, the big change from my perspective is that MS is actually attempting to make CLI administration feature complete; which has historically not been the case, at all, on Windows.
(TL;DR: I in no way deny praise of Powershell’s elegance/architectural power/etc.; but from the perspective of someone with a limited ability to appreciate those virtues, the big deal is that Powershell coincides with MS moving to make CLI a first class UI and expose a lot more of what traditionally had no CLI mechanisms to work with.)