4 ms·

I sure love it when my shell takes seconds to load on startup.

by oynqr 5y ago

kimbernator 5y ago
It is easy to go overboard with oh my zsh for sure, but startup time, as long as it's less than ~5 seconds, is not likely to be a big problem for most people. On slower machines the real killer is the time it takes for the next prompt to appear after each command. There are mitigations, but I've definitely had machines where it is almost unbearable.
- nemetroid 5y ago
  Five seconds really is unusably slow, in my opinion. Even a tenth of that is grating. If I want to run a one-off command, I open a new terminal to do so, and close it when I’m done.
- animal_spirits 5y ago
  My pretty extensively customized zsh config with ohmyzsh takes maybe a quarter of a second to load... Maybe I don't have as customized config as I thought because if it is taking a second or more I can't imagine what is being loaded.
- deleted 5y ago
  [deleted]
sgarland 5y ago
~/.zshrc:L1:"zmodload zsh/zprof" ~/.zshrc:EOF:"zprof" Doesn't take long to track down the culprits. nvm is a huge contributor to startup lag, IME. I am not a frontend dev, and rarely have to touch Node, so I comment out anything nvm-related for daily work.
- eyelidlessness 5y ago
  For folks who use nvm and find it slow, try out Volta[1]. It’s much faster, and IMO a lot nicer to use in general. 1: https://volta.sh/ https://volta.sh/
- rustyminnow 5y ago
  Nvm startup times are the worst. I use it to install npm versions, but then manually add those to my $PATH. There's a --no-use flag that short-circuits all the heavy startup processing, but still gives you access to the command. Here's a snippet from my zshrc: ``` export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" --no-use export PATH="$HOME/.nvm/versions/node/v14.17.6/bin:$PATH" ```
- krinchan 5y ago
  I just use nodenv via anyenv. All the ${X}vm utilities have massive startup lag for some reason.
- nerdponx 5y ago
  Yet another NVM alternative is FNM, which is very fast. I'm surprised there are so many others!
- chrisweekly 5y ago
  I agree nvm is suboptimal. I've been doing web-related things for a living since 1998 and I care about tooling. YMMV but I have a strong preference for managing node versions via `n` (installed via tiny util `n-install`). My Node-related macOS terminal setup: - iTerm.app - zsh (via brew) - n-install -> n -> node (/npm) - yarn (via npm i -g) - pnpm ("") HTH! :)
vlunkr 5y ago
I hear this argument from zsh purists all the time, I'm pretty sure it's made up. I've used oh-my-zsh for years with several plugins and the startup time is basically imperceptible. Maybe it's slow if you're running on raspberry pi or something.
- soraminazuki 5y ago
  Not a raspberry pi but a Macbook.
  - smoldesu 5y ago
    Yeah, I can't quite comprehend what makes the terminal experience on MacOS feel so sluggish. At first I thought I was being spoiled by Alacritty, but even Konsole feels more responsive than iTerm these days.

I sure love it when my shell takes seconds to load on startup.

by oynqr 5y ago

I sure love it when my shell takes seconds to load on startup.

It is easy to go overboard with oh my zsh for sure, but startup time, as long as it's less than ~5 seconds, is not likely to be a big problem for most people. On slower machines the real killer is the time it takes for the next prompt to appear after each command. There are mitigations, but I've definitely had machines where it is almost unbearable.

nemetroid 5y ago
Five seconds really is unusably slow, in my opinion. Even a tenth of that is grating. If I want to run a one-off command, I open a new terminal to do so, and close it when I’m done.
animal_spirits 5y ago
My pretty extensively customized zsh config with ohmyzsh takes maybe a quarter of a second to load... Maybe I don't have as customized config as I thought because if it is taking a second or more I can't imagine what is being loaded.
deleted 5y ago
[deleted]

sgarland 5y ago

~/.zshrc:L1:"zmodload zsh/zprof" ~/.zshrc:EOF:"zprof" Doesn't take long to track down the culprits. nvm is a huge contributor to startup lag, IME. I am not a frontend dev, and rarely have to touch Node, so I comment out anything nvm-related for daily work.

eyelidlessness 5y ago
For folks who use nvm and find it slow, try out Volta[1]. It’s much faster, and IMO a lot nicer to use in general. 1: https://volta.sh/ https://volta.sh/
rustyminnow 5y ago
Nvm startup times are the worst. I use it to install npm versions, but then manually add those to my $PATH. There's a --no-use flag that short-circuits all the heavy startup processing, but still gives you access to the command. Here's a snippet from my zshrc: ``` export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" --no-use export PATH="$HOME/.nvm/versions/node/v14.17.6/bin:$PATH" ```
krinchan 5y ago
I just use nodenv via anyenv. All the ${X}vm utilities have massive startup lag for some reason.
nerdponx 5y ago
Yet another NVM alternative is FNM, which is very fast. I'm surprised there are so many others!
chrisweekly 5y ago
I agree nvm is suboptimal. I've been doing web-related things for a living since 1998 and I care about tooling. YMMV but I have a strong preference for managing node versions via `n` (installed via tiny util `n-install`). My Node-related macOS terminal setup: - iTerm.app - zsh (via brew) - n-install -> n -> node (/npm) - yarn (via npm i -g) - pnpm ("") HTH! :)

vlunkr 5y ago

I hear this argument from zsh purists all the time, I'm pretty sure it's made up. I've used oh-my-zsh for years with several plugins and the startup time is basically imperceptible. Maybe it's slow if you're running on raspberry pi or something.

soraminazuki 5y ago
Not a raspberry pi but a Macbook.
- smoldesu 5y ago
  Yeah, I can't quite comprehend what makes the terminal experience on MacOS feel so sluggish. At first I thought I was being spoiled by Alacritty, but even Konsole feels more responsive than iTerm these days.