Comment by dempedempe
5 hours ago
It's like this with a lot of things now. For example, Nix's learning curve used to be a huge barrier to entry. Now with LLMs, I'm using nix-darwin and home-manager for dotfiles, package management, and have individual flakes in all of my projects for cryptographically reproducible builds!
Nit: there’s nothing “cryptographic” about reproducible builds.
“Reproducible build” already usually implies bit-by-bit reproducibility.
“The reproducibility is cryptographically verifiable with hashes“ would be the full sentence, but it’s a mouthful.
I meant with Nix you're comparing hashes. With Docker, you're using pinned versions
i thought it mainly implied architectural/hardware compatibility and deterministic output
Nix is also great at work. You keep the server nix code in the same repo and OpenCode can just change and test server config.