That’s not true with mise. You can add something to the front of PATH in front of mise bins and mise will respect that.

CodeRabbit's support for mise is greatly appreciated, not only do i depend on CodeRabbit for code reviews but CodeRabbit is also a partner level sponsor for mise and my other open source work: https://jdx.dev/sponsors.html

thanks so much!

i benchmarked it locally a few weeks ago and it's much faster than homebrew 7

how much faster is kind of a useless metric: it's so highly variable on which command and things like network speed, expect 2x-1000x faster depending on what we're talking about

someone should make flattendallas.com as a joke

i was going to say the biggest reason wasn't mentioned here, that github sets Disallow: /*/wiki*

however I think maybe this has changed? I don't see it in https://github.com/robots.txt now

They're not indexed if they're publicly editable

also the repo needs 500+ stars https://docs.github.com/en/communities/documenting-your-proj...

It also needs to be non publically editable.

In other words, spiritually not a wiki.

i just tested and `mise bootstrap` is over twice as fast at installing when a bottle was in the cache. other commands like `status/check` are 20-30x faster. that's without spending much work at all on perf—i'm sure i could bring these numbers down much further.

no, in fact you don’t even need node or npm to install npm packages with mise. (You likely will need it to execute them though)

this makes no sense to me, the reason i don't give anyone else the commit bit is only to _protect_ the supply chain. you should want as few people with that access as possible.

I think the concern is more if something happens to you or stop development for any reason, then the project is dead or would fork in a few separate directions

The bus factor makes no sense to you?

https://en.wikipedia.org/wiki/Bus_factor

do you have any kind of succession plan in place in case you get incapacitated for one reason or another? anyone you trust enough for that?

Yes I have a friend that can access my GitHub if I were to die and he would be in charge of deciding who would lead the project

i thought the same thing but i bought a model y a few months ago and turns out that's exactly what I want. 90% self driving and really the 10% is entirely the last part of a drive because it picks stupid parking spots and doesn't know how to enter my driveway, other than that it's driven perfectly

well, perfectly is a bit much, it doesn't know how to dodge potholes yet and it sometimes misses exits/turns, but it's never done anything i would call dangerous

Pothole avoidance is on their “coming soon” list in the last few software update notes. It can’t come soon enough!

for skills related to specific cli tools, i just wrote a standard for this! it's obviously not widely used yet, but since mise will support installing the skills alongside the tool, i suspect it will have decent adoption

i used to be a bit bearish on skills—thinking that llms should just use --help, but i've come around on that. i think skills are a great way to describe higher level workflows that use multiple commands.

https://jdx.dev/posts/2026-09-05-introducing-packslip/