Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For me, because I jump from project to project, different versions and languages, is just perfect to use the same mise commands, and I know it's going to work.

Also I like having a global portable ~/.config/mise/config.toml file.

What I'm not sure yet is how to mix it with brew on Mac OS, so far what I do is, everything I can install with mise, I do, so I know it will work in linux as well, and everything else with brew.

There are exceptions like postgres, which seems available in the registry (asdf:mise-plugins/mise-postgres) but then you need to do:

brew install gcc readline zlib curl ossp-uuid icu4c pkg-config

My rule is, everything that doesn't have brew dependencies and is in mise registry or plugins, I install it from there, everything else from brew. But I'm curious, what's your approach ?

The creator of mise has written about it [1] but I don't think he switches from mac to linux:

> I tend to basically just use core plugins. I like mise for managing things where I really care about the major version (like node). If it's something like shfmt or jq I don't really care about the version. I just want the latest and for me, I find brew to be better suited to that purpose.

- [1] https://mise.jdx.dev/how-i-use-mise.html



I follow what you've quoted at the end of your post. I only use mise for things I need multiple versions of.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: