I'm interested in the topic in general, but not in explaining that declarative systems don't solve the problem of continuously changing software (e.g., for security updates, changing landscape), and the need to update configs that goes along with it. Hope that helps!
Except that things change as well in (or rather "around") declarative systems, and you have to update your config files as well. That's because the underlying software changes, and it has nothing to do with whether your system is declarative or not. You just need to put in the work to update your configs at a different point in time.
For everyone who doesn't have several different systems to maintain, I find the advantages of nixOS to be marginal. Sure, you can argue about atomicity and all, but honestly I don't remember ever running into a serious problem with debian either. The huge package repo is nice, but I rarely encounter an app I can't get through apt, flatpak, or as an appimage.
At the same time, nix also has various downsides. Documentation sucks. There are two main ways to manage the system, they both pretend to be the better one, and it's super hard to even get started. That's not an issue with the technology, but just a lack of priority. Guix is much better on that end (but also comes with the same marginal advantages).
On the other hand, debian has a stable community, with proper processes, democratic structures etc.
This is a nice, kind of old presentation from debconf, where people discussed nix and how this could be useful in a debian context as well:
haha, that would be hilarious! If that is true and you could actually identify here by the mere fact that there is only one possible woman - that would be so amazing (and of course bleak, but also fun!)
This is not generally true and depends very much on where you live. In my hometown, the water was so hard, it ripped the washing machines. Next town, different water source, no issues at all.
Maybe that's when someone cut the lower half of the graph?