We did a blog post a while ago sharing why we decided to use nix for all package management aspects of the framework. Take a look: https://ihp.digitallyinduced.com/blog/2020-07-22-why-ihp-is-...

From the blog post...

> Additionally Nix is very hard to install. This is a stumbling block for a lot of people. Especially when using certain macOS systems you cannot even install nix at all. Luckily most of the nix problems, like the macOS issues will be solved with time.

Great choice

Install nix? Already done. What's the second step?

Why is installing nix any worse than installing some language-specific package manager?

Nix causes a visceral negative reaction in some people.

Why?

It's a complete end-to-end solution with an opinionated approach and unstructured documentation.

That is, the learning curve is very steep.

That said, for new projects I'm doing packaging and containerization in nix, because I don't have the time or mental energy to deal with half-assed solutions anymore.

> I don't have the time or mental energy to deal with half-assed solutions anymore.

Exactly. I'd rather solve a problem in Nix then try some working, but half-baked alternative.

I looked at nix a while ago, concluded the versioning/chesumming is - a given sum should represent kind-of the same thing, but can mean really anything.

There was even a post on how to have a stable version for a tracking branch.

Now, I wouldn't mind, if it were explained exactly what guarantees the hashing provided, but there seemed to be pervasive misconception on what it provides.