mise VS direnv

Where are you getting "mise uses asdf" from? mise is simply compatible with all asdf plugins. Not the same thing.

It's even said almost at the top of the README.md in the "30 seconds demo" section:

"The following shows using mise to install different versions of node. Note that calling which node gives us a real path to node, not a shim."

https://github.com/jdx/mise?tab=readme-ov-file#30-second-dem...

So yes, mise does not use shims. It only manipulates $PATH. I did benchmarks a while ago and that definitely and consistently has shaved some milliseconds off of the startup times of my tools.

mise borrows the plugins from asdf, which also makes it non-cross platform. Interesting discussion on this topic on their GitHub: https://github.com/jdx/mise/discussions/66

Solutions considered include adopting the vfox plugin system or transpiling all asdf plugins to ShellJs.

Now I know that vfox exists.

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 handled and documented.

direnv + mise does exactly that. When I cd to various directories I get different env vars, it's pretty neat. Setting aliases would just be a case of adding them.

https://github.com/jdx/mise/discussions/1525 for an example of how I use direnv with mise.

https://mise.jdx.dev/direnv.html

https://mise.jdx.dev/templates.html

Installed bun js runtime (I used mise, btw)

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.

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).

I think direnv already does a good job in this space, and it's already available in your package manager.

https://direnv.net/

I switched from asdf to mise after a comment on lobste.rs[1] suggested I do so a few months ago, and I have been very happy with it.

It sands off some of asdf's sharp UI edges and provides a somewhat larger but still reasonable feature set; I've also replaced most of my direnv[2] usage with it.

The mise -> asdf comparison page is useful[3]

1: https://lobste.rs/s/66uxbj/how_love_homebrew#c_mvmsjp

2: https://direnv.net/

3: https://mise.jdx.dev/dev-tools/comparison-to-asdf.html

I also made the export diff configurable, motivated by this post: https://github.com/direnv/direnv/pull/1233

Nice.

For years I've been using [direnv](https://direnv.net/) for this, setting environment variables which git picks up. This looks like a more feature complete equivalent, although to be honest I only really need switching of committer email and the SSH key used.

Direnv, for the uninitiated, loads and unloads environment variables when directories are entered and exited. Under every project folder there is a `$PROJ_DIR/.envrc` which contains:

buffer-env: A pure-Elisp version of the direnv utility. Useful to make Emacs aware of Python virtualenvs (which, judging by the questions posted here, is unfortunately still a complication for a lot of people). Similar to (and inspired by) envrc, but doesn't require the direnv program.

You can look at direnv to see this in action as they wrote shell hooks that get loaded into the shell profile and are executed on every prompt. https://direnv.net/

Yes, most Nix users employ https://direnv.net or the equivalent for your IDE of choice. Emacs for instance has https://github.com/purcell/envrc which set per-buffer variables.