logoalt Hacker News

aiono12/08/20247 repliesview on HN

This is already a solved problem with Nix shell (except the task runner part). I don't understand why there are any other alternatives still being developed. Nix supports more packages than any other solution, it's battle tested and cross platform (didn't try on Windows but on Mac OS it works fine). And it's more reproducible than any other package manager.


Replies

jdxcode12/08/2024

I started writing mise in a bout of frustration after trying to use nix

show 3 replies
nextaccountic12/08/2024

I really want nix to succeed, but it has terrible UX and documentation. It also doesn't help that the community is still fighting over whether flakes should be a thing.

show 3 replies
pxc12/08/2024

> This is already a solved problem with Nix shell (except the task runner part).

devenv, a Nix+direnv-based solution, has a pretty cool task runner thing, plus service management.

> I don't understand why there are any other alternatives still being developed.

I love Nix and I believe it's a great choice for many teams, for the same use cases as mise. Nix's paradigm is the future. But Nix's defects are also real and obvious enough if you use it for long. I can understand why someone might see value in trying a fresh new effort, or an approach that asks less commitment.

klysm12/08/2024

Docs are terrible, writing new packages is difficult, etc. It may be the right technical direction but the execution is lackluster

show 1 reply
bloopernova12/08/2024

Because some people may not want nix. Mise is, in my experience, much easier to get into and start using.

srid12/08/2024

> This is already a solved problem with Nix shell (except the task runner part)

The task runner part is also solved in Nix. See

https://github.com/Platonic-Systems/process-compose-flake

and

https://github.com/juspay/services-flake

lijok12/08/2024

Because Nix has dogshit UX and the team seem to be completely oblivious to it regardless of how many times it's brought up.

show 2 replies