asdf VS mise

This, but here are some things I've learned to do:

* Use a .local directory under my home directory instead of ~/bin. That's a great prefix when installing from source or tarball at the user level, keeps the top-level of the home directory from getting cluttered with /share /lib /include /etc /lib etc. etc.

* Reach for the package manager first when installing new software, unless there is a good reason not to. It makes keeping things up-to-date easy, and since I use Arch, which uses a rolling release, you pretty much get the latest stuff.

* If I can't get what I want from the package manager, I'll look at what is available using asdf-vm (https://asdf-vm.com/), and failing that, build from source or install from tarball.

* I don't use snap or the like.

I gave up on Windows over 20 years ago, and I can't say enough how liberating it has been. One of the nicest things is that there is a distro for almost every need (see https://distrowatch.com/). I use Arch; but your use case may point to a beginner-friendly distro, such as Mint, Ubuntu, etc., or a repeatable install type of distro, such as NixOS or Guix, or many others.

# Download asdf git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.15.0 # Add the following to ~/.zshrc . "$HOME/.asdf/asdf.sh" # Optional: Completions are configured by either a ZSH Framework asdf plugin # or by adding the following to your .zshrc: fpath=(${ASDF_DIR}/completions $fpath) autoload -Uz compinit && compinit

asdf is a popular version manager that uses a technique called "shimming" to switch between different versions of tools like Python, Node.js, and Ruby. It creates temporary paths to specific versions, modifying the environment to ensure that the correct version of a tool is used in different projects. However, this method can introduce performance overhead due to how these shims work.

I use asdf and direnv to manage my toolchain at the project level, so to improve the integration with Emacs I installed envrc.

Use asdf (https://asdf-vm.com/) to manage your Ruby versions.

You should be able to do

$ asdf plugin add ruby

$ asdf list all ruby (you'll see 3.4.1, the latest is available)

$ asdf install ruby 3.4.1

And now you can use Ruby 3.4.1 with no issues. Follow that up with

$ gem install bundler

$ gem install rails

$ rails new ...

The toolchain can be installed via Rustup, or (my preferred way) using asdf.

To help you manage different versions of python, node, awscli, cargo the usage of mise will be demonstrated.

Curious how different is this from mise and ubi? https://github.com/jdx/mise

I have a few pain points with that for installing cua (https://github.com/trycua/cua/issues/27), so if it can remove the initial friction happy to chat!

mise (https://mise.jdx.dev/) and dagger (https://github.com/dagger/dagger) seem like nice candidates too!

Mise can install all your deps, and run tasks

For version managers I've switched to using mise - https://mise.jdx.dev/ - supports pretty much everything, all in one place. I have it managing java, node, php, and even tools like awscli, gitleaks, and anything else that might be needed to get a project up and running by a new developer.

This is a great article -- I really appreciate the author giving specific examples. I have never heard of mise (https://mise.jdx.dev/) before either, and the integration with the saved prompts is a nifty idea -- excited to try it out!

Just going to plug https://mise.jdx.dev as a perfect accompaniment to uv. It simplifies installing tooling across languages and projects. I even install uv via mise, and it uses uv under the hood for Python related things.

First, what is mise?

In this post, I’ll walk you through how I use mise to tame the chaos of multi-language development, complete with a mise.toml example to configure a project.