3 ms·
I found that Mise handles all my needs for development and it is scoped so it doesn't try to update Python and break all my virtual env when I install something
by Sytten 13d ago
I found that Mise handles all my needs for development and it is scoped so it doesn't try to update Python and break all my virtual env when I install something new /shrug
- hk1337 13d agoI split my usage. Homebrew for OS things mise for the various tooling. The only problem some things still have a dependency on requiring python and others on the system. The problem being that they’re there, mise works just fine.
- impulser_ 13d agoYou can use mise for install homebrew items btw so if you get a new computer you just drop the config.toml inside the mise and install. This is all you have to add to the config file: [bootstrap.packages] "brew:git" = "latest" "brew-cask:ghostty" = "latest"
- threecheese 12d agoHomebrew does this as well, I keep my packages synced with a Brewfile in chezmoi. Obv this only works for brewed packages though.
- 9dev 13d agoWhy would you even use python without uv anymore, and have a system python binary and virtual envs linked to it?
- atmosx 13d agoPython might be just one of the languages required by the dev stack not the only language. Mise is the right tool for the job.
- 9dev 13d agoLast time I checked, Mise is still a one-man show. That’s way too risky for a critical party of my supply chain for my taste.
- doodlesdev 13d agoSo is sudo... And that's not "too risky" for the entire industry. That's not to say bus factor is irrelevant (I personally think about it a lot when choosing software projects), but truthfully the bus factor here especially doesn't matter much, as mise is an easy tool to replace (with asdf, for example) if something goes wrong with it eventually. I highly recommend trying it out. I resisted using it for some time, but it solved some pain points I had with NodeJS, Ruby, and Python regarding installation.
- 9dev 12d ago> So is sudo... And that's not "too risky" for the entire industry. Sure it is, and that's why I'm looking forward to systemd's Run0 -- but for now, there's just no way around the sudo package. That's different for Mise, though, because there are a lot of ways to work productively without it. I'm not fond of consciously adding supply chain vulnerabilities to our stack when I don't have real pain to do so.
- doodlesdev 11d ago> Sure it is, and that's why I'm looking forward to systemd's Run0 -- but for now, there's just no way around the sudo package. Regarding Run0, I'd prefer to not rely so much on Polkit authentication after crazy vulnerabilities such as PwnKit (a pkexec vuln, but a good reminder that moving the security boundary won't magically solve issues). > I'm not fond of consciously adding supply chain vulnerabilities to our stack when I don't have real pain to do so. I SUPER agree with you on that, btw. It's just likely that mise solves a problem which is much bigger for me than it is for you. Honestly, I'd prefer if I could manage everything with my distro packages, but, for a multitude of reasons, they're rarely enough for development tooling with multiple versions and environments.
- bodash 13d agomy split: brew for casks, mise for tools
- artdigital 13d agoI also started using Mise for global CLI tools instead of brew and it’s working really well Eg: mise use -g gcloud instead of brew install xxx It can even do that for npm packages! Like mise use -g npm:xxx
- acedTrex 13d agoMise is really sloppily vibe coded these days
- kstrauser 13d agoWhat broke and affected you?
- zymhan 13d agoOkay
- brachkow 12d agomise also can manage brew