I think it was an idea who's time had come. Declarative WoW has been gaining momentum as git has been incorporated into more and more dev flows (ex: CI automati

I think it was an idea who's time had come. Declarative WoW has been gaining momentum as git has been incorporated into more and more dev flows (ex: CI automation declared in repo is now standard). Nix or Guix is just a natural extension to that. Maybe combined with some general dependency-hell frustrations out there. I agree that it feels like the popularity has increased a lot recently (though I don't think I have any real evidence for that more than personal experience) but I would personally just put that down to a slow organic growth over a long time which suddenly pushes a technology closer to the mainstream and then there could be a sudden inflection point of attention to it. Maybe network effect is the better description. Sudden increases like this also often comes with a bit of a counter wave. See the "RIIR" jokes for example. I can definitely understand those feelings. It is annoying when something is brough up constantly and talked about as a panacea to everything. Nix will (and already have had) this quite a bit. Especially since nix probably deserves criticisms more than most. Even with flakes it is still very hard to understand and can limit the amount of people able to make changes to the build pipeline. To these critics I can just say that I understand and that it is perfectly fine to not switch to nix. We are just trying to find solutions to problems we see and have had in our projects, they might not be good solutions problems existing in yours.