impermanence

Look, I try to avoid bringing up nix in unrelated conversations. But. > The only two options I have is a) do a factory reset and reinstall software from scratch and spend time configuring things again, or b) live with all of the extra garbage that has been excreted by the software on my systems just so that I can keep the data that I actually want to keep. NixOS solves this. > My ideal system would separate data that was written because of me (non-default config values, bookmarks, etc) from documents etc made by me, from garbage that the program wants to write that I absolutely do not care about and do not want to know about. And NixOS with https://github.com/nix-community/impermanence does this, forcefully. Actually normal nix might solve it depending on how far you want to go. Again, I wouldn't usually try to evangelize it, but you have

> As an example, nixos keeps state around regarding user id/username mappings, to avoid giving the same user id to different users across time. So a fresh install of nixos might leave services unable to read their data files, because the file might be owned by a different user id. One reason to set `mutableUsers = false`: https://mynixos.com/nixpkgs/option/users.mutableUsers. > And if you activate and enable incus, for instance, it will probably create a bridge device: the device will remain in place after you remove incus, which will have implications for how your network/firewall works that your configuration will depend on but will not enforce or be able to reproduce. Impermanence: https://github.com/nix-community/impermanence. To be clear, I don't use neither. But you can get NixOS to be almost completely stateless (if this is somethi