

Managing 30+ machines with NixOS in a single unified config, currently sitting at a total of around 17k lines of nix code.
In other words, I have put a lot of time into this. It was a very steep learning curve, but it’s paid for itself multiple times over by now.
For “newcomers”, my observations can be boiled down to this: if you only manage one machine, it’s not worth it. Maaaaaybe give home-manager a try and see if you like it.
Situation is probably different with things like Silverblue (IMO throwing those kinds of distros in with Guix and NixOS is a bit misleading - very different philosophy and user experience), but I can only talk about Nix here.
With Nix, the real benefit comes once you handle multiple machines. Identical or similar configurations get combined or parametrized. Config values set for Host A can be reused and decisions be made automatically based on it in Host B, for example:
- all hosts know my SSH pub keys from first boot, without ever having to configure anything in any of them
- my NAS IP is set once, all hosts requiring NAS access just reuse it implicitly
- creating new proxmox VMs just means adding, on average, 10 lines of nix config (saying: your ID will be this, you will run that service) and a single command, because the heavy lifting and configuring has already been done, once -…
AFAIK I’m neurotypical… No, trains of thought like these are common (see also other respondents on here), and they can also happen in the blink of an eye. It’s just that when the question or comment has formed, I’ll make a mental note to either ask/mention it later after the current topic has concluded, if I think the other person also has interest in hearing it, or to google it later if not. Or to just drop the thought if I come to the conclusion that it doesn’t matter all that much to myself either.