I'm not the author and my opinion might not be warranted, but I would guess: * When you modify your local nix file, there's only a couple things you need to ch

I'm not the author and my opinion might not be warranted, but I would guess: * When you modify your local nix file, there's only a couple things you need to change. It stays small. You can keep track of all these changes because they're in your head. * The company needs a lot of little changes here and there so they build up. Foobar needs rooster v1,2 while Barfoom needs rooster v0,5. A lot different than managaging a users config. No longer possible to squeeze all the details into one brain. This isn't to say Nix would be bad at handling any of these things. But I would agree with the OP. I have trouble teaching new devs how APT and shell work. Couldn't even imagine trying to explain Nix syntax to them. The more Nix is used for, the more likely a dev will have to touch it. And teaching someone who doesn't care Nix is like teaching someone who doesn't care about Makefiles / Git. Doesn't work. They just get mad and say it's too complicated.