6 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 4d 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
- zymhan 4d agoOkay
- 9dev 4d agoWhy would you even use python without uv anymore, and have a system python binary and virtual envs linked to it?
- atmosx 4d 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.
- zbentley 4d agoTrue, but Python is the one with an env management system (venv) which is the most prone to breakage for projects that depend on system Python. Uv is far superior to both mise and Homebrew for Python work, and I find that it removes the vast majority of pain preventing me from using Homebrew by default for most things, and mise only occasionally for specific dev envs.
- 9dev 4d 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 4d 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.
- jdxcode 4d agothis 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.
- weaksauce 4d agodo 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?
- jdxcode 4d agoYes 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
- OberstKrueger 4d agoI 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
- hk1337 4d 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_ 4d 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"
- bodash 4d agomy split: brew for casks, mise for tools
- artdigital 4d 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 4d agoMise is really sloppily vibe coded these days
- kstrauser 4d agoWhat broke and affected you?