Nix forked, but over politics instead of progress
www.theregister.com
Aux.computer fragments the community – but doesn't fix the technological objections

…except Liam can’t decide whether to be a boomer or a piss baby about it.

  • taanegl@beehaw.org
    2·
    7 months ago

    I guess he has a Proven track record…

    *pauses for laughter*…

    Laugh, you bastards!

    In any case, I think this guy misses the point regarding /nix/store naming conventions, particularly the dependency graph hash after every package name. This little brilliant thing basically tells you all you need to know about it’s association. It’s also part of why you can have several packages from several different closures without resorting to adding -1, -2, etc.

    That being said, I have been eyeing Guix because of how the nix community was run… but let’s see how things go.

  • David Gerard@awful.systemsEnglish
    1·
    7 months ago

    Liam adds in the comments section

    Nix fans love it with a passion I have only seen previously for horribly obsolete text editors, but the odd thing is that they mostly keep quiet about it, which TBH I find a very endearing characteristic.

    • pyrex@awful.systems
      1·
      7 months ago

      They most certainly do not keep quiet about it!!!

      – a person who has posted about programming on Mastodon

  • corbin@awful.systemsEnglish
    0·
    7 months ago

    While the author is being a bit of a tool, they’re right about one thing: everybody who jumped the gun prior to the board announcement is now left with an ostrich-sized amount of egg on their face and no obvious path towards reconciliation other than eating a very large omelette. In particular, Jake and the Aux team don’t have an obvious technical roadmap, which is a serious problem for a nixpkgs fork; also, I feel bad for Xe, who has left the community entirely and condemned themselves to pre-Nix distros. Pride leads to hubris leads to self-flagellating blogposts.

    …I say, as I continue quietly working on my own reimplementation of Nix…

    • self@awful.systemsM
      0·
      7 months ago

      that’s my biggest frustration with Aux. they’ve actually dropped the nixpkgs fork after the board announcement, but I haven’t seen many concrete plans after that. there’s so much low hanging fruit for improvement on NixOS’s mechanisms and processes and I’d love for someone to take a swing at fixing all that — but I don’t think Aux is currently anywhere near focused enough to be it

      at least we got Lix out of things, which I think is an incredibly important project to have especially after the board announcement. Nix’s new governance structure has a gigantic gap in it in the form of the Nix evaluator, and I feel strongly that’s intentional. having an independent and modernized (but compatible) Nix implementation will be better for the ecosystem as a whole.

      I’d love to hear about your Nix implementation when it’s in a shareable state. I’ve got a few Nix-related projects myself that need a good home — some finished ones are waiting for things to fully settle before I decide how they’ll be released, but one project I’d like to start (but don’t know where it should go) is much better directory-local evaluation — that is, lorri/nix-direnv/use nix but with just one vastly-improved implementation in the evaluator.

      • corbin@awful.systemsEnglish
        3·
        7 months ago

        Yeah, Lix is good. It’s not what it claims to be, but just being a CppNix fork is enough.

        So, I’m not developing in secret. My code is here, in my rpypkgs flake, and as the .packages.${system}.reguix attribute of that flake. One would probably want this Cachix cache if they’re on amd64 and want to avoid building PyPy or CPython. (Upstream discussion about this bootstrap path is here.) I’ll send out a more serious round of invites once the lexer, parser, compiler, and evaluator can actually handle a real-world evaluation.

        For posterity: Hi! I’m linking this to you because you’d like to contribute to Regiux. Cool! You need to know RPython, a dialect of Python 2.7 used to specify interpreters. In a nutshell, RPython is statically-typed with lots of metaprogramming, somewhere around Java or Haskell. You write a Python 2.7 program, it gets imported into memory, and then the RPython toolchain compiles from memory into C, optionally generating a JIT compiler. For a gentle explanation, check out Brown et al doing Brainfuck (1, 2); if you’d like to see what high-performance RPython looks like, check out my DIVSPL interpreter or my take on Brainfuck.

        • self@awful.systemsM
          4·
          7 months ago

          that’s awesome, and RPython seems like a great choice for a more comprehensible foundation for a Nix evaluator! I’ll definitely be digging into this more as time permits this weekend. feel free to start a thread for this if you’d like more eyeballs on it at any point in the future!