jdx

I make dev tools. I love CLIs.

[jdx @jdxcode]

@MenasheMichelle @WestminsterWAG what about "premium economy only" or "business class only" bins? mere suggestions?

[jdx @jdxcode]

@FlamesAdvocate @bradluttrell it's safer in part because there is very little chance of a person or object entering the parking space while you're backing in vs the street. You're reversing into a place far less likely to have anything in it in the first place.

[jdx @jdxcode]

@travisennis @nateberkopec Generally yes, although prek also manages tools but hk does not

[jdx @jdxcode]

Eh it was the other way around… I loved the name so much I was hoping the conflict with a ruby library wouldn’t conflict too much. I dont think I would make the same decision today, on the other hand it’s really hard to find a purely unique name anymore. mise wasn’t unique either

[jdx @jdxcode]

@clemensk @nateberkopec I think long-term the biggest benefit is that aube is lockfile agnostic so you don't need to convert a project over to it like pnpm or need to pay attention to what package manager a particular project uses—aube works with any project out of the box.

[jdx @jdxcode]

@travisennis @nateberkopec I would argue no. hk has far deeper integration with linters and is more advanced as a result especially in terms of parallelism.

[jdx @jdxcode]

@dimitrispan @dhh I can't answer your question about extra, but I can say I've been in conversation with an arch maintainer to start automating the bumps to mise and other packages.

[jdx @jdxcode]

@owenyuwono @dhh I would do the same, I also don't think mise is great for managing rust. Some ecosystems just have awesome idiomatics around version management that mise gets in the way for.

[jdx @jdxcode]

@lachie_h I am getting pretty good at lockfiles after having done it for both mise and aube lol

[jdx @jdxcode]

. @supabase is the newest sponsor for mise/en.dev! thanks so much! https://t.co/Fisnt1hVvt

[jdx @jdxcode]

@grok @Ladyesther369 @thevivafrei @grok wow. it’s crazy to me the legal system hasn’t worked out something that sounds to me as simple as theft.

[jdx @jdxcode]

@grok @Ladyesther369 @thevivafrei Sorry @grok but I don’t think I’ve heard another example of "corporate vs consignment before". Feel free to enlighten me though

[jdx @jdxcode]

mise/en.dev has its first premier-level sponsor! Thanks to @37signals @dhh! https://t.co/Fisnt1hVvt

[jdx @jdxcode]

@pudgenet @memeticsisyphus right. When traffic gets backed up it causes problems in other places. Human queues don't have this problem.

[jdx @jdxcode]

Thank you to @coderabbitai for being the first company to formally sponsor mise and my other projects through https://t.co/b6JKD4YEsA!

[jdx @jdxcode]

kudos to @TheDanBlanco for giving me the "mise" npm package so you'll be able to `npm i -g mise` instead of `npm i -g @jdxcode/mise` in the next mise release

[jdx @jdxcode]

@moraes_c_ thank you!!

[jdx @jdxcode]

@SamMorrowDrums I don’t think so, I think for an agent to truly not be able to do something it needs a sandbox or a separate machine

[jdx @jdxcode]

Should I default mise to 24h minimum release age? (We have the feature but the default is disabled)

This would probably cause nonzero issues, but my guess is y’all would like this enough for it to be worth it.

[jdx @jdxcode]

@caiobchi I’d hesitate to draw a line over what exactly a "runtime" is and why. A decision like that makes mise confusing. This seems better suited to you having a custom exclusion list.