4 ms·
The biggest visible boost has been in my shell startup times. Buying a computer after 5 years with 4 times as many cores and it feeling just as sluggish because
by tecoholic 2y ago
The biggest visible boost has been in my shell startup times. Buying a computer after 5 years with 4 times as many cores and it feeling just as sluggish because nvm and pyenv are parsing the same set of bash files reading from disk was not pleasant. Mise actually made me feel, I didn’t just throw the money into a void
- jdxcode 2y agoI don't understand how people don't notice the massive tax they're paying by using nvm: $ hyperfine "~/.nvm/nvm.sh" "mise env" Benchmark 1: ~/.nvm/nvm.sh Time (mean ± σ): 1.722 s ± 0.032 s [User: 0.064 s, System: 0.112 s] Range (min … max): 1.684 s … 1.805 s 10 runs Benchmark 2: mise env Time (mean ± σ): 13.4 ms ± 5.7 ms [User: 10.0 ms, System: 21.3 ms] Range (min … max): 9.4 ms … 42.2 ms 29 runs Summary mise env ran 128.14 ± 53.94 times faster than ~/.nvm/nvm.sh 100x is definitely something you'll notice EDIT: for some reason in discord we're getting very conflicting results with this test. idk why, but maybe try this yourself and just see what happens.
- paulddraper 2y agoI notice. It's awful.
- porridgeraisin 2y agoI prefer GitHub.com/tj/n. It's really nice.
- httgp 2y agoI switched to https://github.com/Schniz/fnm https://github.com/Schniz/fnm a while ago and it’s been fantastic. I also bake it into all of our Packer images at work.
- NunoSempere 2y agoI built my own version on nvm (called nsnvm, for "Nuño's stupid node version manager") to solve this. You can see it here: https://github.com/NunoSempere/nsnvm https://github.com/NunoSempere/nsnvm Absurdly fewer features (and might break npm install -g), but very worth it for me for the reduced startup times.