[q3k]

Right, the problem is that this leaky abstraction effectively now requires you're both good at Nix and good at fixing whatever tool it is that is refusing to work with Nix. That usually means diving deep into build systems, code that makes wrong assumptions, and probably other hairy topics. In return you do get a state of the art system, but you very often need to put in work you otherwise wouldn't need to.

I don't mind that because that's how my brain is wired, but there's plenty of people who don't give a shit and Just Want Things To Work Out Of The Box. Nix(OS) is certainly not for everyone.

[soraminazuki]

I don't see what the problem is. What Nix is doing is far more transparent than the article's preferred solution of Docker images. While Docker images are entire distros crammed into a binary blob, Nix derivations are inspectable and customizable. Nix uses standard mechanisms to configure software, like config files and environment variables. It really isn't black magic.

Also contrary to popular opinion, Nix configs are actually easier to comprehend and maintain than configs written in Chef, Ansible, or Kubernetes. Having a proper language for describing large and complex pure data helps.