Why do some teams use Nix for ML reproducibility?
hardAnswer
- Nix: purely functional package manager.
- Every build fully specified — bit-for-bit reproducible across machines + time (unlike pip / conda which can differ).
- Every dep of a dep of a dep is pinned.
- Downside: steep learning curve, small ML ecosystem support.
- Popular for regulated + long-term reproducibility (medical, financial).
- Alternatives: Guix (similar).
- Most ML teams stick with Docker + pip-tools which is 'good enough'.
Check yourself — multiple choice
- Random
- Nix purely functional: every build fully specified → bit-for-bit reproducible; every transitive dep pinned; steep learning curve + small ML ecosystem; regulated/long-term; Guix alternative; most use Docker+pip-tools 'good enough'
- Same as pip
- Not real
Nix: bit-for-bit reproducible; regulated / long-term; alternative to Docker+pip.
#reproducibility
Practise MLOps & Data Quality
215 interview questions in this topic.