https://chaos.social/@ktemkin/112392108881500298
https://chaos.social/@ktemkin/112392108893774195
This isn’t just a fork of Nix—this is the work of a team of 10+ people near-constantly since early February. (Technically, us too — but our task is really just enabling others.)
Some serious work has gone into ensuring it improves on upstream without having the regressions that have plagued them last three major versions!
And, since this will matter to some — it’s not a project of the NixOS foundation, but an independent organization that takes its responsibility to its community seriously.
What makes this different from https://aux.computer? And with just ten people - such a small community, to maintain what, a parallel fork that will eventually be forced to accept patches from Nix repos? How does it protect against, let's say, corporate decisions? Wouldn't that seep into their project too? Not trying to demotivate them, but I fear that this could be the fate of their project.
There's Guix, which is an official GNU project. If anyone is willing to learn a little bit of Guile Scheme - look, the language is great, the project isn't contaminated with multiple scripts, project skeleton is much better, the modules are well written, so why not move over there? Sure, it's still in the early version, so some stuff will be hard to work with, but personally, I think it's a really nice hard-fork.
https://forum.aux.computer/t/the-future-of-nixcpp-lix/483
The announcement resolves one of my last fears for Aux: development on Nix itself. It is no secret that the number of people knowledgeable about the project and are willing to work on this CPP codebase is small. You have probably seen me mention multiple times by now that @sig_cli needs all of the help that we can get. Lix resolves this entirely with a trusted team of experts. This means that Aux is now able to remove Nix development from our priorities and can instead collaborate with Lix moving forward.
Oh, so from what I see, Aux is responsible for working on the Aux tooling, which is basically Nix CLI fork. And Lix is the operating system itself, including infrastructure and clones of Nix essentials like Nixpkg, Hydra, etc? I could definitely see these folks collaborating with each other.
Aux is still keeping all of their code on Microsoft GitHub, Lix isn’t
Does nix package manager have some issues adressed by this implementation or was it born for another reason?
The short version is that community lost faith in nix governance.
Oc the og based gigachad PhD holder didn't just force through a RFC which causes thousands of regressions in the main repo. Nix community is sure healthy under this kind of leadership.
