Another Weakness: The Nix repository is voluminous, but if your fhs binary has not been packaged, then you need to create a build derivation, which is not straightforward. The more prosaic strengths however need to be reiterated I think. Incremental, declarative, reproducible & super stable. You can build your system 'block by block', as it were (Nixos is inherently very modular), and although it sometimes needs debugging, it simply is very hard to break. As it is declarative, repairing any kind of problem is very simple, you simply revert to a previous build. It is reproducible in the sense that you can create a very highly configured Operating System, and then by declaring the code elsewhere, (e.g. copying & pasting the code into a new build), you replicate the system, at very little time cost. At the risk of repetition, Nixos is not ephemeral - your build, and the effort that goes into the build, is useable for the foreseeable future.......
Another Weakness: The Nix repository is voluminous, but if your fhs binary has not been packaged, then you need to create a build derivation, which is not straightforward. The more prosaic strengths however need to be reiterated I think. Incremental, declarative, reproducible & super stable. You can build your system 'block by block', as it were (Nixos is inherently very modular), and although it sometimes needs debugging, it simply is very hard to break. As it is declarative, repairing any kind of problem is very simple, you simply revert to a previous build. It is reproducible in the sense that you can create a very highly configured Operating System, and then by declaring the code elsewhere, (e.g. copying & pasting the code into a new build), you replicate the system, at very little time cost. At the risk of repetition, Nixos is not ephemeral - your build, and the effort that goes into the build, is useable for the foreseeable future.......