Instructions make it clear that nix needs to be checked.
Why?
It replaces many disparate package management systems for many languages, and Linux system libraries etc. (where traditionally operating system package manager would be used), or Anaconda / Node, with one principled approach that seeks to precisely specify every antecedent -- no matter whether OS or ecosystem -- with a recursively hashed derivation from a tree of dependencies.
Dockerfile approach: Write instructions to build an image. Allows for more flexibility, but less reproducible.
Nix approach: Use declarative language to define dependencies and configuration. Provides reproducible builds and integrates well with Nix package manager.
Instructions make it clear that
nixneeds to be checked.Why?
It replaces many disparate package management systems for many languages, and Linux system libraries etc. (where traditionally operating system package manager would be used), or Anaconda / Node, with one principled approach that seeks to precisely specify every antecedent -- no matter whether OS or ecosystem -- with a recursively hashed derivation from a tree of dependencies.
Better summarized here: https://shareg.pt/2QaIZcB
Dockerfile approach: Write instructions to build an image. Allows for more flexibility, but less reproducible.
Nix approach: Use declarative language to define dependencies and configuration. Provides reproducible builds and integrates well with Nix package manager.