> Are we talking about the same autotools? Yes. Instead of figuring out how to do something particular with every single software package, I can do a --with-foo or --without-bar or --prefix=/opt/baz-1.2.3, and be fairly confident that it will work the way I want. Certainly with package managers or (FreeBSD) Ports a lot is taken care of behind the scenes, but the above would also help... - Source: Hacker News / about 2 months ago

The Elixir and Erlang communities have long been popular for installing and managing multi-version environments through asdf. Asdf is also a general-purpose version management tool, and the ecosystem is so rich. - Source: dev.to / about 1 month ago

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions https://asdf-vm.com/. - Source: Hacker News / 2 months ago

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)? These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and… We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s... - Source: Hacker News / 2 months ago

Https://asdf-vm.com/ ASDF is better because it works with many more languages, other than only Python, like Rust, Go, Node, etc, and other tools, such as AWS/Google/Firebase/Azure CLIs. - Source: Hacker News / 2 months ago

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise). - Source: dev.to / 4 months ago