In reply to @irenes:matrix.org
which is a fair position but like... the world does have state. I don't think it's really right to build an abstraction that says there's never state. I think there's a missing counterpart to nix that deals with exactly the things nix doesn't - stuff that shouldn't be version-controlled or multi-homed for security reasons; backups; figuring out what you even have...

i don't think it should be saved personally. i think that most of it should be burned down and rewritten and relegated to a secondary component. we wouldn't drop support, we would just go put it in a corner where it doesn't need a lot of maintenance. the good features would be generalized, and the good ideas taken to make something new of the ashes.

flakes are a cute little lock file manager, and the schema would be a lot more useful if flake = true; inputs actually supported putting my own nixpkgs with overlays into them. if i could actually use the schema, it would be useful. but such as it is. a lot of the fancy flakes libraries tend to make it all a lot worse by forcing all the inputs unnecessarily, causing gratuitous downloads and making it impossible to stub inputs (cough flake-parts).