3 ms·
I read the project's Readme and all I'm left with is "why?". I use Devbox[1] and get access to the entire Nix ecosystem, done. [1] https://github.com/jetify-c
by mootoday 2y ago
I read the project's Readme and all I'm left with is "why?".
I use Devbox[1] and get access to the entire Nix ecosystem, done.
[1] https://github.com/jetify-com/devbox https://github.com/jetify-com/devbox
- Zizizizz 2y agoMise just works and takes maybe 1-2 minutes to explain and have a tool running on a team members machine in my experience. I couldn't get into nix, too complicated for me and I've yet to find a resource that makes it click for me. After that I would feel comfortable encouraging the rest of the team to use it but as mise is so easy and even more popular, I will probably just stay using this. I will look into devbox though, thank you for the recommendation!
- mootoday 2y agoI hear you, Nix has been nothing but a waste of time for me every time I tried to do anything with it. Devbox abstracts it and the only time I had to do a nix-specific thing was when I needed a flake to install a CLI from a GitHub release.
- goku12 2y agoThere are multiple tools in this space - even devbox has a direct competitor. With mise, I'm not expecting an isolated environment, but rather a meta package manager. I can install many tools directly into my user shell. If I wanted that with nix, I would be using a nix user install rather than devbox. You just choose what you like most. And mise seems to have a large fanbase.