A new PowerShell session takes anywhere from *five to thirty seconds* just to give me a prompt I can type at.
Blame it on the other software if you want, but PowerShell isn't just a little slow. It's hundreds of times slower than any interactive shell should be.
The part of my PowerShell profile that takes the most time to execute is removing all of the fake, useless aliases for Unix commands that PowerShell bundles and refuses to remove.
>learn to use your machine.
Now, you can keep whining for next decade, or fix your problem and stop this millenial shaneningas.
I think consensus would more likely support "learn to keep your machine from using you".
I am a wizard. My profile is my power. With great care and sacrifice I've got it down to about 2s and I just have to load less-commonly-used stuff ad-hoc.
I have a 3900X with 64gb of ram and a recent ssd.
Powershell startup time is the number one problem with the tool, GP is correct.
For example, many people keep each function in a separate file, instead of merging them into psm1 during build. That will speed it up A LOT.
You can have different profiles and load them when you need them, even when you enter specific folder.
There are ways around it. You complain that you want everything everything everything loaded in advance for your wizardry but are u really a wizard if you can't solve this? So if you buy a porche and then put a house on top of it, shop in cart in the back of it, tires for every season, and so on, and then complain its slow, then guess what...
> Pwsh starts on my machine in 400-500ms. Far slower than I'd like. That is with no profile.
This is already 10x slower than a reasonable shell startup time, with no profile configuration at all, on an extremely fast desktop system. It's downright embarrassing that you are even attempting to defend this state of affairs.