3 ms·
From the bottom-up, the core problem Nix solves is that of programmatically expressing package composition, in terms of reproducible builds [0]. For instance, i
by mindslight 5y ago
From the bottom-up, the core problem Nix solves is that of programmatically expressing package composition, in terms of reproducible builds [0]. For instance, it does away with the common notion of ambient "system libraries", and instead makes it so every single dependency is specified by the build file. If you've ever compiled a compiler and followed the folk advice to do three stages, or did cross compilation and had to juggle build/host/target triplets, Nix takes those patterns and expresses them executably.
Nixos extends this reproducibility up to the level of the OS. Rather than a machine being a giant ball of mutable state, some of it pushed around by configuration management, Nix pulls the entire system state up to a single top value which is set by the bootloader (or similar high-level mutable cell). Like switching to functional programming, at first it just appears different, difficult, and not compelling. But after you start to understand the paradigm, a lot of nice capabilities just fall out, that would otherwise be effectively out of reach.
[0] Not deterministic builds per se, which is an ongoing effort.