Lix
lix.systems
Lix is an independent variant of the Nix package manager, developed by a team of open-source volunteers, and maintained by and for a passionate community of users.

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.

    • lemmyreader@lemmy.mlOPEnglish
      361·
      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.

        • veaviticus@beehaw.org
          14·
          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.

    • Shareni@programming.dev
      16·
      6 months ago

      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?

      The language is great, but the ecosystem is on life support, and I don’t see it getting anywhere close to nix soon. I believe it’s especially crippled by being Linux only and forcing free software to the point you’re not allowed to even mention the non-free repo in the guix irc.

      Random Devs and companies aren’t going to use it for their projects, and so there far less maintainers to solve issues like having a node version that’s not in maintenance for half a year and 4 major versions behind, or having automated npm package conversions.

      Realistically it’s currently only useful for a few languages with abysmal PMs, most of which are lisps, and like Haskell.

      • Shareni@programming.dev
        61·
        6 months ago

        Now that I think of it, a guix fork would be far more useful than a nix one. You could forgo some of the FOSS extremism, and allow your users to install it without an ethernet cable, and maybe even on the infidel Operating Systems (even though guix is in the official repo for Debian + wsl).

        And I bet guile could really use the attention. AFAIK it’s mainly developed by one dude, and he made some impressive improvements. Just check out the release speeches on youtube, massive jumps between versions.

        Best of all, the GNU people could focus on building a better core, and choose to adopt only some changes, while preserving the purity of their system.

        • nixfreak@sopuli.xyz
          2·
          6 months ago

          I would be for that fork. I used Guix a long time ago and got really frustrated with non-free and binaries. Guix is really nice to use though and it’s fast.

      • M. Orange@beehaw.org
        2·
        6 months ago

        Aux is only keeping the code on GitHub temporarily because money is tight and there are very few options for a soft fork of a repo as huge and active as nixpkgs. Plus, they want ease of accessibility for devs considering it’s a very new project.

        Long term plans are to move off of GitHub. I’m pretty sure some people are talking to Codeberg to see how feasible it would be to move there in the future.

        • toastal@lemmy.ml
          1·
          6 months ago

          I would believe that when I see it. They said they would not use GitHub-only features & they already are. These things don’t tend to move once actually set up. You also look at the language around trying to “cast a wide net” being thrown out before “what are our principles” & compromising on that so early is a big oof from me. Folks that can’t be bothered to create a new account or learn a new forge or version control system are not the folks that would be bothered to switch from Nix to Aux.

          Literally any other option would offer easier escape …with the exception of the size of Nixpkgs & the fact that most developers don’t understand how to do patches without a pull request on the host platform rendering the D in distributed version control system moot so everyone clamors nothing can scale without Microsoft (allow requests off the centralized forge, allow patches to a mailing list, seed it with Radicle, etc.). The foundations are being built wrong.