Live data from Hacker News

The Nixpkgs core team has disbanded

discourse.nixos.org

51–60 of 221 posts

Re: The Nixpkgs core team has disbanded

#51
post #47

Earlier quoted context omitted.

I suggest giving Bazzite a try

I tried Fedora Silverblue and I found its notion/implementation of immutability fairly frustrating. It’s actually the reason I went to nixOS. It seemed to me that it was all the friction of immutability without any of the benefits of reproducibility.

https://stagex.tools

Re: The Nixpkgs core team has disbanded

#52
post #39

Earlier quoted context omitted.

https://www.redhat.com/en/blog/pluggable-authentication-modu...

What does this have to do with installing packages?

I don’t have all of the details, sorry, but PAM is a bunch of .so that are dlopen'd and if you mess them up you lose access to your system pretty damn quick. I would tell people to just use the system libc but I don’t know the specific failure modes for using libc via Nix. Using system libc = building your project outside of Nix.

There could be similar issues with NSS but I think more people are ready to bypass NSS altogether.

Re: The Nixpkgs core team has disbanded

#53

There was a sweet spot in like 2024 when it seemed like everything was possible with Nix, but now it seems like everything “experimental” is permanently so (like flakes), packages I care about are not as fresh as I want, I have no mental recall for Nix commands… Meanwhile, my company is using Nix for everything heavily internally. Everyone gets their dependencies via Nix unless you are like using PAM or something. Re…

Is your company paying anyone to develop nix?

Re: The Nixpkgs core team has disbanded

#54

There was a sweet spot in like 2024 when it seemed like everything was possible with Nix, but now it seems like everything “experimental” is permanently so (like flakes), packages I care about are not as fresh as I want, I have no mental recall for Nix commands… Meanwhile, my company is using Nix for everything heavily internally. Everyone gets their dependencies via Nix unless you are like using PAM or something. Re…

Can you share more about what made you move away?

I’ve been running a NixOS based homelab for awhile now with 5 physical hosts and about 30 NixOS containers/VMs in an Incus cluster and I can’t imagine moving away from my central Nix repo and ability to rebuild/upgrade the entire fleet in one command and feel confident that things will work.

While I’m concerned about the disbanding, it would take quite a lot to make me look elsewhere, and there’s enough critical mass that I feel confident others will step up.

Re: The Nixpkgs core team has disbanded

#55
post #48

For anyone reading this and jumping to a broader conclusion: the Nixpkgs core team disbanding does not mean Nixpkgs or Nix is dying. It does mean that this particular structure was not sustainable, very important contributors burnt out and we need to do better, faster. We need to continue learning from this and continue building a stronger ecosystem that prioritizes the contributors who are the only reason any of thi…

> more than anyone can imagine two people doing

The core team was just 2 people and they disbanded?

There was also a steerco for just 2 people?

I’m now even more confused.

Re: The Nixpkgs core team has disbanded

#57
post #47

Earlier quoted context omitted.

I suggest giving Bazzite a try

I tried Fedora Silverblue and I found its notion/implementation of immutability fairly frustrating. It’s actually the reason I went to nixOS. It seemed to me that it was all the friction of immutability without any of the benefits of reproducibility.

I'm convinced that some day bootc (or something similar) will be exactly what I'm looking for, but not yet.

Re: The Nixpkgs core team has disbanded

#58

Earlier quoted context omitted.

Is it really that complicated? I personally use direnv with nix to have per-project dependency versions installed automatically, and I’ve never had too much trouble. I know that the flake.nix files can become somewhat complicated, but mine have been pretty simple thus far.

I didn’t use the word “complicated”, maybe I’m missing something, but I listed some specific complaints and “Nix is complicated” wasn’t on the list.

Not OP, I’m not really sure what your specific complaints are based on the original comment. They seemed more like general/nonspecific concerns, which left the comment pretty open to interpretation.

Re: The Nixpkgs core team has disbanded

#59
post #48

For anyone reading this and jumping to a broader conclusion: the Nixpkgs core team disbanding does not mean Nixpkgs or Nix is dying. It does mean that this particular structure was not sustainable, very important contributors burnt out and we need to do better, faster. We need to continue learning from this and continue building a stronger ecosystem that prioritizes the contributors who are the only reason any of thi…

> more than anyone can imagine two people doing The core team was just 2 people and they disbanded? There was also a steerco for just 2 people? I’m now even more confused.

Here's the team's description https://nixos.org/community/teams/nixpkgs-core/. They were able to accomplish quite a lot of useful work. The steering committee is a separate organization (https://nixos.org/community/teams/steering-committee/) that contains more people and arguably accomplishes less.

Re: The Nixpkgs core team has disbanded

#60
post #48

For anyone reading this and jumping to a broader conclusion: the Nixpkgs core team disbanding does not mean Nixpkgs or Nix is dying. It does mean that this particular structure was not sustainable, very important contributors burnt out and we need to do better, faster. We need to continue learning from this and continue building a stronger ecosystem that prioritizes the contributors who are the only reason any of thi…

The Nixpkgs Core team was established in Sept 2025 (https://discourse.nixos.org/t/establishing-the-nixpkgs-core-...), so it is a fairly new concept and idea. They've accomplished some good things as highlighted in the post, but are now stepping down. Yes, we'd prefer for the team to exist, but we've also functioned without one for ~20 years. It may take multiple iterations to bootstrap the concept and to figure out the right structure - or we may find it isn't needed. So no, this is not a critical emergency. It's a return to the status quo of late last year.

That being said, I think it is still a concept worth pursuing.

Post reply on HN