2 ms·

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 s

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.

9dev 13d 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.