Linked by Drumhellar on Thu 6th Sep 2012 02:43 UTC
Windows "Windows Server 2012 probably won't have the adoption lag in the enterprise that Windows 8 is bound to face. That's because, aside from the Metro GUI, Server 2012's biggest changes are in substance rather than style, building upon what the company delivered with Windows Server 2008 Release 2 three years ago. In particular, Server 2012 takes two management features Server 2008 R2 admins will be familiar with - Server Manager and PowerShell - and expands on them considerably."
Thread beginning with comment 534087
To read all comments associated with this story, please click here.
by Lennie on Thu 6th Sep 2012 13:24 UTC
Member since:

Actually, I'm not a fan of PowerShell. It's freaking slow.

Reply Score: 4

RE: PowerShell
by n4cer on Fri 7th Sep 2012 01:00 in reply to "PowerShell"
n4cer Member since:

Actually, I'm not a fan of PowerShell. It's freaking slow.

In startup time, runtime performance, or your workflow (i.e., using the language)?

The startup time for PowerShell 3.0, at least on Windows 8/Server 2012 (haven't tried it down-level, but it should be similar) is near instant (on par with opening Command Prompt).

Runtime performance should be faster over prior versions as well, in part, due to the new, DLR-based engine, .NET 4.5 optimizations, and general optimizations to PowerShell itself.

The language has gained a few shortcuts and simplifications for some scenarios, but their value it's largely subjective if the language is what you're criticizing.

Reply Parent Score: 3

RE[2]: PowerShell
by Lennie on Fri 7th Sep 2012 08:15 in reply to "RE: PowerShell"
Lennie Member since:

I haven't checked all the other properties of the langauge or runtime, but this is a scripting language.

Startup time is really, really important. Without good startup time a scripting language is almost useless from the start.

Reply Parent Score: 2