Linked by Drumhellar on Thu 6th Sep 2012 02:43 UTC
Permalink for comment 534158
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
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.
http://blogs.msdn.com/b/powershell/archive/2012/06/14/new-v3-langua...
http://technet.microsoft.com/en-us/library/hh857339