The Nixpkgs core team has unfortunately decided to disband. We’re proud to have had the opportunity to lead by example in bottom‐up, consensus‐focused governance for Nixpkgs, and of our achievements over the past 10 months, including reforming the committer delegation process and onboarding 19 new committers, empowering maintainers by extending the merge bot, re‐establishing contact with GitHub and securing the sponsored Enterprise Cloud upgrade, helping triage GHSA-67f2-674w-6g63 and track the...

TL;DR: Two of the most nicest, most technically proficient people you know just got burnt out from contributing to their operating system and this is just another example of NixOS being poorly maintained.

A year since I divested from NixOS and nothing really has changed. The “flakes” design is still a garbage abstraction invented by a neo-nazi to sell to Peter Thiel and Co. The Nix language has not evolved in any meaningful way (nixpkgs is still the load bearing peg).

Nixpkgs has reached over 1 million commits and is pushing what Git can scale to and is now entirely dependent on a Microsoft GitHub enterprise subscription and a Amazon AWS S3 credits for petabytes of CI/CD.

The community still contains active MIC fascists in leadership roles alongside :votevote Europeans. empoc perspectives are treated as community fracturing.

The nix derivations abstractions has not truly caught on (due to it not even being better than containers resource wise) and flakes only makes this worse with unversioned commit hashes serving as “determinism” and “reproducibility” which have become buzzwords at this point.

I only expect this to get worse and worse as Determinate Systems (MIC ghoul company) takes over and nixpkgs collapses as an independent entity.

BTW they haven’t decided on a AI/LLM policy because the steering committee and the nixpkgs core team can’t agree or communicate on anything, which basically means NixOS is going to be a AI hype train project if you enjoy that.

  • ZWQbpkzl [none/use name]@hexbear.netEnglish
    9·
    2 months ago

    Maybe. I haven’t fully looked into btrfs snapshots because I’m not ready to move off my complicated LUKS on LVM setup. I also don’t think you can simply select a previous version from boot menu like with NixOS or rpm-ostree. I’d frankly be happy with SteamOS’s A/B partition scheme. I haven’t seen a guide on how that’s implemented though.

    • Inui [comrade/them]@hexbear.netEnglish
      8·
      2 months ago

      CachyOS, which is based on Arch, offers Limine as a default bootloader. You can boot snapshots directly from that. I came from using Bazzite for the last 2 years and that fills one of the major advantage gap my atomic setup had over my current one.

      • ZWQbpkzl [none/use name]@hexbear.netEnglish
        3·
        2 months ago

        Btrfs will work on top of a luks or lvm device but it seems silly to use it with lvm since it replicates many of lvm’s features. Normally you would do lvm on luks and replace lvm with btrfs. But since I’m doing luks on lvm I can’t replace lvm with btrfs. btrfs on luks on lvm is possible but it really eliminates most of btrfs features.

        What is opensuse using to generate those grub entries? Does that come with snapper or is it something else?

        • swelter_spark@reddthat.comEnglish
          2·
          1 month ago

          I had to search around a bit to find out. The grub2 snapper plugin in the Tumbleweed repo includes a script in grub.d that adds btrfs snapshots to the boot menu.