3 ms·

While it can be faster, you must be using Commodore 64 or something. Or you have Defender running or something... It starts instantly, anything else is your loc

While it can be faster, you must be using Commodore 64 or something. Or you have Defender running or something... It starts instantly, anything else is your local problem. Please stop spreading nonsence and learn to use your machine.

Havoc 4y ago
It's slow AF on multiple machines my side too so he is not alone. >learn to use your machine. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- majkinetor 4y ago
  Yeah, its becoming ridiculous, but somebody needs to say it like it is. I, along with other people I am working with, used it on litterally thousands of different machines, during last decade. I think I have a pretty good experience about its speed, and while its not millisecond snappy, its not a picture you people are makig. If its slow, its a local problem, period. VM, AV, too many slow modules on autoload, slow profile, it could be a bunch of things. Now, you can keep whining for next decade, or fix your problem and stop this millenial shaneningas.
  - eviks 4y ago
    But I've fixed my problem by switching away from pwsh. You see, those "many modules" are what made pwsh usable
- fuzzfactor 4y ago
  >learn to use your machine. I think consensus would more likely support "learn to keep your machine from using you".
pxc 4y ago
Where I work, my laptop runs a bunch of agents I have no choice about, some of which are related to Windows Defender. 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.
psd1 4y ago
Pwsh starts on my machine in 400-500ms. Far slower than I'd like. That is with no profile. 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.
- majkinetor 4y ago
  That depends on the modules you use. 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...
  - pxc 4y ago
    Uh, let's back up. > 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.
    - majkinetor 4y ago
      Your shell is not comparable to pwsh, because pwsh contains everything under the universe already there, while in typical shell, you need to install 3rd party tools, and then load them as you use them. I don't feel embarrased at all, while you should be, by comparing apples and oranges.
      - pxc 4y ago
        PowerShell's slowness doesn't have anything to do with its feature completeness, though, nor the capabilities of the language itself. Many new shells inspired by PowerShell's structured pipelines and built-in coreutils replacements share both of those features with it, but not its abominable slowness.

Havoc 4y ago

It's slow AF on multiple machines my side too so he is not alone. >learn to use your machine. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

majkinetor 4y ago
Yeah, its becoming ridiculous, but somebody needs to say it like it is. I, along with other people I am working with, used it on litterally thousands of different machines, during last decade. I think I have a pretty good experience about its speed, and while its not millisecond snappy, its not a picture you people are makig. If its slow, its a local problem, period. VM, AV, too many slow modules on autoload, slow profile, it could be a bunch of things. Now, you can keep whining for next decade, or fix your problem and stop this millenial shaneningas.
- eviks 4y ago
  But I've fixed my problem by switching away from pwsh. You see, those "many modules" are what made pwsh usable
fuzzfactor 4y ago
>learn to use your machine. I think consensus would more likely support "learn to keep your machine from using you".

pxc 4y ago

Where I work, my laptop runs a bunch of agents I have no choice about, some of which are related to Windows Defender. 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.

psd1 4y ago

Pwsh starts on my machine in 400-500ms. Far slower than I'd like. That is with no profile. 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.

majkinetor 4y ago
That depends on the modules you use. 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...
- pxc 4y ago
  Uh, let's back up. > 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.
  - majkinetor 4y ago
    Your shell is not comparable to pwsh, because pwsh contains everything under the universe already there, while in typical shell, you need to install 3rd party tools, and then load them as you use them. I don't feel embarrased at all, while you should be, by comparing apples and oranges.
    - pxc 4y ago
      PowerShell's slowness doesn't have anything to do with its feature completeness, though, nor the capabilities of the language itself. Many new shells inspired by PowerShell's structured pipelines and built-in coreutils replacements share both of those features with it, but not its abominable slowness.