Wow you pushed it even further, nice !!!
That makes a lot of sense; since a flake-parts module can define any number of flake outputs, it can also address things that link two kinds of outputs that aren’t of the same kind. This is not so easy with plain nixosModules.
I don’t wish to complicate my system configuration(s) with this pattern for now.
I think that a good configuration is modular in the sense that someone can take any one file of mine, and move it into their configuration, and it will more or less work. That only works if their configuration is made of the same kind of modules as mine, i.e. nixosModules.
In short: flake-parts modules blows the complexity budget for newcomers, and I’d like if my NixOS configuration is readable and adaptable by newcomers, since this is the most valuable personal project you can have for getting onboarded into the ecosystem.
Still, this pattern is very cool. I’d definitely consider using it for Nix-heavy projects, and it is very nice to know there’s an example of it here, so thanks a lot for it.
Just a suggestion for anyone who wants to collaborate on the dendritic pattern to set up a “watch” for any of PRs, discussion and issues.