Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by 6u54wuwu5w on Friday November 18, 2016 @07:28AM
(#12986254)
So, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?
[ Parent
| on HN ]
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by richard_todd on Friday November 18, 2016 @08:17AM
(#12986486)
Funny, that was my first thought as well. Sometimes I start cmd.exe instead of powershell on rotating-disk machines because of the startup time. On SSDs I find the startup time is negligible.
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by Aldo_MX on Friday November 18, 2016 @09:14AM
(#12986857)
That's my biggest concern, I actively avoid PS just because I can't tolerate its startup time.
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by louhike on Friday November 18, 2016 @08:16AM
(#12986479)
It's better but it's still slower than CMD on my computers.
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by algorithmsRcool on Friday November 18, 2016 @08:19AM
(#12986502)
In particular if you have left the prompt window untouched for a few hours and it has been paged out. Just pressing <tab> to complete a file name will hang for 3-6 seconds on my computer while PS wakes back up.
CMD is always instantaneous.
I realize that PS is doing a lot more work to match commands but sometimes simple is all that is needed.
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by JeffreySnover on Friday November 18, 2016 @09:21PM
(#12991664)
Major improvements in V5.
Even more in V5.1 (which ships with WS2016).
But still slower than CMD.
CMD starts very quickly but then you have CMD. :-)
Jeffrey Snover [MSFT]