wpyoga

Is it possible to load the dynamic libraries before fork()ing and somehow prevent the path lookup and library loading? This will open up new possibilities for hardened security models.

Apologies for the delay. Now I do notice a delay when using the asdf shim instead of running the binary directly. But it's nowhere near 900ms.

I'm on a T480s with i5 CPU and SSD:

  $ time node --version
  v18.13.0
  
  real 0m0.080s
  user 0m0.079s
  sys 0m0.027s

  $ time ~/.asdf/installs/nodejs/lts/bin/node --version
  v18.13.0
  
  real 0m0.009s
  user 0m0.006s
  sys 0m0.003s

I have been using asdf for over a year now, and I haven't seen `node -v` take so long. Actually, I used to use nvm and it was much slower than asdf, which was my main motivation to switch.

I'm wondering if the lack of slowness I've seen could be due to my simplistic setup: globally set nodejs version, single nodejs version installed, with other tools like git installed by the distro package manager. I also have golang and some other stuff like rclone installed using asdf, but not much more.

Did you also have a similar experience when initially installing node? Did you notice what triggered it or when did asdf start to become slow?

I like asdf and would like to avoid making it slow on my laptop.

Oh and can I safely assume that your home directory is on an SSD and not on an HDD?