7 ms·

Python 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 3d ago
  True, 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 ago
  Last 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 ago
    So 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 ago
    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.
    • weaksauce 3d ago
      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?
      • jdxcode 3d ago
        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
    • OberstKrueger 3d ago
      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