3 ms·
I think your experience is atypical. I use powershell everyday and I've not noticed any startup time difference between it and cmd. Are you sure you don't have
by AnIdiotOnTheNet 8y ago
I think your experience is atypical. I use powershell everyday and I've not noticed any startup time difference between it and cmd. Are you sure you don't have some gigantic import in your profile.ps1? Are you launching the really terrible and definitely slow as balls to launch Powershell IDE?
Frankly, given how superior powershell is as a language (both to cmd and bash) it is beyond me why anyone would consider a small startup cost difference a dealbreaker anyway.
- Macha 8y agoI've got no powershell customizations, and an i5-4670k. I've also experienced Powershell having a very noticeably slow startup. It's about on par with my heavily modified zsh setup on a 2015 MBP for startup time (the same zsh setup starts up much faster on the same desktop). It's not a dealbreaker, but it's definitely an annoyance.
- AnIdiotOnTheNet 8y agoVery strange. My work rig is a downright geriatric Core2 Quad @ 2.66Ghz. There has to be some reason for the difference.
- gobio 8y agoI think it's pretty typical: powershell is slower to start up than cmd. On my machine, i7, 16GB RAM, Windows 10, the fastest is cmd (instantaneous), then powershell (1s) and bash WSL (1s), then supper slow default install of git-bash (12s!). I cannot use git-bash because of that.