|
|
|
|
|
|
by romwell
2890 days ago
|
|
|
Sure, sure, more functionality. That's not an excuse for the startup time of a shell not being instantaneous on a modern system. To harness the power, I write Powershell scripts (yay no more batch files), but it's just too annoying to experience the startup lag to use the shell for the simplest tasks (e.g. simply running a console application). That shouldn't be the case. PS: "modern object-oriented" was all the hype in the 80-s. It's not an excuse for a performance hit today :) |
|
|
If you're running Hyper, note that this alone takes 6s to (warm) start Cmd on my 16GB RAM Core-i7 Surface Pro 4.
PowerShell takes ~1.2s to (warm) start connected to Console, while also starting a half dozen modules and scripts in my PowerShell user profile.
PowerShell takes < .7s to start when run with `-NoProfile`