subtooting, NixOS
You know, if you want the #NixOS build system to keep using Nix instead of Lix, maybe you should be spending your time fixing Nix bugs instead of pearl-clutching on the issue tracker about how unfair it is that they've switched to a fork that actually works?
subtooting, NixOS
Or alternatively, y'know, actually fixing those governance issues in Nix that people have been telling you about for half a decade
subtooting, NixOS
"But it takes time to fix governance issues! We can't do that overnight!"
Okay, so then how did Lix successfully avoid these issues in a fraction of the time? Do you think that perhaps the problem lies with your perspective on the issue, and not with the proposed fix?
subtooting, NixOS
To make it a little more explicit: Nix follows (a variant of) a 'benevolent dictator' model, whereas Lix follows a 'collective decisionmaking' model.
One of those models is remarkably improving the quality of the software right now, and it sure isn't the 'benevolent dictator' one.
subtooting, NixOS
@joepie91 And not to snipe ourselves, but I do think that the Lix model suffers from a lot of shortcomings and still can do much better.
But forking is difficult, and getting there was already difficult, but we have still growing to do (and a project should really never stop growing and questioning its governance state, etc.).
subtooting, NixOS
@raito Oh, I'm sure it's not perfect! But that last paragraph is the crucial one - I think it is the main responsible factor for Lix working as well as it does, and it is crucially also a very difficult (if not impossible) philosophy to implement in a 'benevolent dictator' model.
subtooting, NixOS
@joepie91 I fully agree with you. I just wanted to make it clear there's more on the path, and I am with you on the fact that departing from BDFL is critical and urgent for a project of this size and this importance.