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/

I'm biased but I think it's silly to think either one is going away anytime soon

well mise uses dotenvy right now (for env._file anyhow), it may be worth switching to dotenv-ng but I haven't looked into it yet https://github.com/jdx/mise/blob/fc441787fe52b46be1245046758...

I assume you just mean normal [env] in mise.toml which is different, but this still is relevant to mise

Yes - I think .env files are not a good idea (works for one person but even then it's not great)

90% of australians live in 0.22% of the country's land

Whole the us has different numbers, but the same point applies. Most of the people in the US live in dense enough areas. The Mid west has similar size and population as France for example.

i think that sentence is taken out of context a bit, the problem with those pkg binaries is that they're not portable—which the post describes

EDIT: actually no, I think charlie is wrong on that point, he said the installers compile python but that only happens with python-build-based installers like pyenv. still, the fact those binaries lack portability is the real problem.

mise uses these as well and adopting them has been a massive improvement in the user experience for my python users. y'all have been doing a fantastic job maintaining them.

i'm also doing the same for ruby—maintaining the binaries myself which is becoming the default in mise next week: https://github.com/jdx/ruby

i'm a firm believer that pre-compiled, portable binaries are the best way to distribute runtimes and clis.

The combo of mise + UV has made my development environment setup/recreation so seamless. We've come a long way.

(Props to your work on mise)