Hacker Newsnew | past | comments | ask | show | jobs | submit | ishanz's commentslogin


Nix package manager: correctly resolves dependency hell for your entire OS.

Nix governance: still hasn't resolved dependency hell for humans apparently.


but the dependency hell for human is inherently political


For a certain definition of "correctly" (namely: it doesn't, it just does what containers do and ships unique versions for every package).


This is not what nix does unless a user configures it poorly. Nix will ship a single, dynamically linked package/version combo for all package that depends on it. Containers ship one for each package that depends on it.


Containers don't solve dependency hell. They just give you a standard way to ship your bespoke bash scripts.

If you like writing bash scripts then go for it. (Personally I'd rather be doing literally anything else, like, I don't know, shoveling manure.)


Containers do solve dependency hell by isolation. It's like venv/uv in Python that you switch between different environment with different sets of dependency. Or speaking essentially, you lifted yourself away from having dependencies shenanigans since you have virtualizations of it


> Containers do solve dependency hell by isolation.

Only if they isolate each atomic package individually. Which is exactly what Nix is and what Docker isn't.


that's what they said


I got the same email

What’s up with the [removed *]


The url was to transfer log data from metabase to framework. It is not something that is intended for end user access.


I don’t love that take. Extreme positions are often where the interesting ideas are, even if you don’t agree with them.


The ideas are alluring because they're extreme. However the relatively boring stuff in the middle is far more likely to reflect reality or be actually useful.


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

Search: