asdf

See also: asdf and mise https://github.com/asdf-vm/asdf/issues/290#issuecomment-2365...

I'm a happy long-term user of asdf. https://github.com/asdf-vm/asdf

While I understand your valid criticism with the overhead of using an interpreted language here, I must point out that using multiple versions in the same repository is quite an antipattern that comes with various complications. Maybe you should consider switching to a version manager of[0] your[1] choice[2]. [0]: https://github.com/jdx/mise [1]: https://github.com/asdf-vm/asdf [2]: https://github.com/version-fox/vfox

For software developers, `asdf`[0] and dockerized projects goes a long way. For provisioning the environment variables needed for development, HashiCorp's `vault`[1] can make that pretty simple. Combine that with `direnv` to have it load the value dynamically with: ``` # .envrc API_KEY=$(vault kv get -field=API_KEY secret/projectA/dev) ``` I also wanted to experiment using `pass`[2] instead, but messing with GPG keyrings and the like is unwieldy and not too user-friendly. It's what I use for personal projects since Vault is overkill. [0] https://github.com/asdf-vm/asdf [1] https://github.com/hashicorp/vault [2] https://www.passwordstore.org/

Looks like pyenv does the same thing as asdf, except only for python. https://github.com/asdf-vm/asdf And here's a list of everything it supports: https://github.com/asdf-vm/asdf-plugins/tree/master/plugins

The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating. I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like. [0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383... [1]: https://github.com/asdf-vm/asdf/pull/1441

Not nix based, but I really like https://github.com/jdx/mise too to manage dev tools. It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.

You might check out rtx[1] Its an asdf[2] rewrite, in rust, that can do most of the things nvm can [1] https://github.com/jdx/rtx [2] https://github.com/asdf-vm/asdf

Presumably https://github.com/asdf-vm/asdf

That's what I would suggest as well. WSL2 and use asdf[1] to manage the erlang/elixir versions. You could also use containers pretty easily as well with docker or podman for windows and the official Elixir images[2]. [1]: https://github.com/asdf-vm/asdf [2]: https://hub.docker.com/_/elixir

You may consider using asdf or some other Python version manager to get a newer (or older) Python https://github.com/asdf-vm/asdf

I'm on an M1 MacBook Pro 16". The performance issues are well understood by the asdf team and the Github issue with most comments is on the topic: https://github.com/asdf-vm/asdf/issues/290 This was with a half dozen plugins and use_legacy_file disabled. Hardly an edge-case. Though I'll note in other tests it was around 200ms (which is the number I put in the README to be fair). @danfritz in this thread said his can take over 2 seconds! Out of curiosity, what is the difference between `time node -v` and `time ~/.asdf/installs/nodejs/*/bin/node -v`? I've never seen it not add at least 100ms.