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.

  • lemmyreader@lemmy.mlOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    6 months ago

    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.

    • LalSalaamComrade@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      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.

      • veaviticus@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        I think that’s backwards. Lix is a replacement for the nix package manager, while aux is a replacement for NixOS.

        Aux looks like it will now use Lix for it’s package manager, instead of trying to make its own fork of nix.