Nix: An idea whose time has come

Re:Nix: An idea whose time has come by haberman on Friday February 18, 2022 @09:03PM (#30393756)

It sounds like this is similar in concept to Bazel, except the output of Bazel is a statically linked binary instead of a binary that dynamically links .so's with known SHAs.

In both cases you have a language that fully specifies how to hermetically and reproducibly build some output artifact(s) based on dependencies that are fixed down to the SHA.

[ Parent | on HN ]

Re:Nix: An idea whose time has come by fooblessmooo on Saturday February 19, 2022 @05:08PM (#30400984)

Nix is repeatable, but not upper-case Reproducible i.e. you don’t necessarily always get the same hash from the same build. Order of operations or concurrency or something like that.

[ Parent | on HN ]

Re:Nix: An idea whose time has come by tadfisher on Friday February 18, 2022 @09:38PM (#30393932)

Dynamic linking is the default in nixpkgs, but Nix itself does not care what you build. So you can use the infrastructure in `pkgs.static` to build statically-linked binaries if you like.

[ Parent | on HN ]