> I've always kept my usage of Nix language to a minimum and found it to be a joy every time. The trouble is, it's more significant to consider what the pain i

> I've always kept my usage of Nix language to a minimum and found it to be a joy every time. The trouble is, it's more significant to consider what the pain is in the worst case. e.g. Two things which count against Nix: With stuff like Docker, I can get away with not really understanding what's going on, and have a quick + dirty fix. And with Nix, the community is smaller, so it's less likely you'll find an answer to the problem you're having right now. I worked at a company where the DevOps team used Nix for the production/staging. For local development (and ephemeral development deployments), the dev team came up with a docker-compose setup. -- That said, there was at least one case where the devs contributed to the Nix stuff by way of copy-pasting to setup a new deployment.