mise

“The best thing about mise is that it's very easy to get exactly what you want, and remove it when you don't want it anymore”

“I'm not fond of consciously adding supply chain vulnerabilities to our stack when I don't have real pain to do so.”

“I believe the primitives mise provides are a key enabler for agentic development in a distributed org and team context”

“It also doesn't work well. And they have no support outside of Discord chat.”

“I primarily use it for installing tools and running tasks, having env support is just a cherry on top.”

“Mise handles more stuff (tool versions, environment vars) and also has nicer ergonomics for specifying tasks”

“the in terminal advertisement for a problematic company I want nothing to do with”

“The combo of mise + UV has made my development environment setup/recreation so seamless.”

“I'd argue it's a good time to play with features since if you have any ideas on how it might better fit your workflow”

“Being able to centralize this config is far more attractive than having a separate Ansible or pyinfra process.”

“I can roll out a new computer in 2-3 commands and have my entire environment configured the way I like”

“mise handle polygot and some things where many versions need to been handled on the same system”

“If you have mise activate set up correctly in your shell rc file, globally installed tools are available in every shell.”

“I found mise's support to be pretty sub-par compared to Shivam Mathur's packaging work for homebrew”

“docker compose is a bit trickier – it gets installed as docker-cli-plugin-docker-compose, but docker-cli doesn't seem to pick it up”

“I personally switched from Mise back to Brew. I don't know if it was just my skill issue, but there were too many packages which found Mise to be problematic.”

“Onboarding a new team member is super easy now, they just need Mise, "mise install" and they're up.”

“The problem is you still have to know to look for that setting to enable it.”

“It has also simplified all of our CI and made the random python projects a breeze to run.”

“Mise is also currently MITMing my shell, along with presumably many other dev machines”

“I use mise everyday - it's basically muscle memory to type "mise" before a command in many of my projects now thanks to mise tasks”

“i think mise does too much. the deeper you go into its features the more rough edges you’ll find.”

“I like mise a lot. As somewhat of a power user I've also found its rough edges though.”

“I use mise to install it in a manageadble way (and basically everything else on my computer).”

“For most of them there's nothing to add though, you simply publish tools on GitHub/Cargo/etc. and mise will know how to install them.”

“Overall there's too many ways to install things and it's not easy to add any of them.”

“I cannot endorse mise more highly. I commit it to my repos to make sure every engineer has the same environment.”

“It manages everything at the user level so it's not as "all encompassing" as Nix and is readily compatible with immutable distros.”

“I initially used nix to manage dev tools, but have since switched to mise and can't recommend it enough”

“others are using Mise or Nix on a per project basis to automate the development environment setup and that works well on GitHub Actions”

“Mise does all the same things as just, but also has source/output tracking to avoid rerunning build jobs”

“I have started writing all logic into mise tasks since I already manage the tool dependencies with mise”

“I'm a fan of it, and I can't think of a reason why I would use asdf over mise. ... they've solved real problems I've had.”

“it starts effectively instantly and works not only for node versions but all programming languages and tools”

“I am migrating all of our GHA to use the mise action. Makes keeping the version of Go, linters, formatters etc. for the project so much easier.”

“It's a single action that installs all relevant tools (and keeps your local dev env in check)”

“mise is awesome and replaces both sdkman, pyenv, and other similar tools that are restricted to one ecosystem.”

“I found the documentation confusing and as so often with general-approach tools too overwhelming for what I'm trying to do.”

“The beauty of mise is that as long as someone is hosting a precompiled binary for you, it's easy to get it.”

“I've had good experiences with it, and it manages Rust, Go, Python, etc. environments very well.”