Technology creates cliques. Some of them formed for good reasons, others maybe not.
The nature of nix prevents the nix community from being a group of like minded people because it tries to be a unifying layer over technology which is not made by like minded people. To do what nix does, you need to overcome whatever forces caused those cliques to form in the first place. You need representatives from each group. It's a bit like congress, which has similar problems.
And its not just disparate language communities. It's people who want to build influential businesses, and its people who want to insulate themselves against the influence of tech business. Its people who think it's OK to build killer robots, and it's people who don't want to be killed by those robots.
Getting people work together is hard. Nixpkgs tries to do that to such a degree that you can put a version number the result. Maybe it's admirable, maybe it's folly. I think it's both.
I'm not going to blame the people who are ambitious enough to try because as far as I'm aware, whatever other successful communities exist, they're succeeding at a less audacious goal.
I really don't think these issues are necessarily "systemic" in the sense that they've been ongoing for the last decade. I _was_ a long-time contributor until about two years ago when certain actors came into the community and started making a bunch of unnecessary drama. Since then I've seen some long-time friends in the community either slowly drop out or simply get ran out by a mob with pitch forks.
“Our experience is that the Steering Committee as an institution lacks a native instinct for the delegation envisioned by the constitution, while also not being sufficiently engaged and cohesive to handle individual decisions at those levels itself.”
This is an almost poetic description of micromanagement. I really like Nix and have been running it as my main OS for several years in the past ~ 10 years.
I don’t think the issues they have are unsolvable, it just appears that the governance model they’re trying to have is not working out, and it’s very difficult to roll back.
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.
Reminds me of Bazel, in the way that it gets adopted by companies with developer support teams (because it solves real problems) but feels frustrating for us ordinary folk. Nixpkgs is kind of a critical part of “ordinary folk” and with the core team disbanding, I feel like my personal moves away from Nix (for projects) are proving correct.
Nix sounded great, but actually trying to use it for personal use felt like a constant time sink. LLMs made it seem like their bespoke language could be side stepped and one could get all the benefits of the ideas without the time sink. But now they have drama, so I hope someone runs with the idea but for humans and possibly LLMs.
Even just reading this has more bureaucracy than at a company with hundreds of people. Holy hell some projects turned open source into committees and committees to decide what committees are needed.
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 this is possible.
Personally, I'm sorry and grateful. Sorry that it ended in core folks being burnt out. Grateful since they did some of the most amazing work, more than anyone can imagine two people doing.
1. the "I used nix once/some time ago but I realized it's stupid/hard/whatever"
2. anime pfps/furries/trans/woke are bad
3. complaining about CoC/governance/etc
Irrespective of whatever the posted article is about relating to this technology. This is one of those threads.
Nix seems to have one of the worst discussion quality around here. Rust threads are similar (though they got better recently), specially on the negative unrelated comments side, but seem to have much more engaged people. Maybe Anubis has a similar ratio. I wonder why?
Hopefully a new governance structure will emerge and allow for a better path forward.
As a layman who has only used AI to package a couple things on NixOS for personal use, I would think that LLM agents are perfect for taking over most of the nixpkgs workflow.
So, looks like that being a good manager and serving it is no that easy for a good engineer in the end.
(I'm not snarking at Nixpkgs core team, just at the many HN readers there that hate engineering managers in general just because they had some bad experience personally)
Very telling that you think it’s comparable. An engineering manager doesn’t manage a random bunch of international people, but a smaller group of (company culturally) vetted people.
40 comments
[ 0.28 ms ] story [ 35.0 ms ] threadFor too many, building and celebrating things just because they are cool isn't enough.
The nature of nix prevents the nix community from being a group of like minded people because it tries to be a unifying layer over technology which is not made by like minded people. To do what nix does, you need to overcome whatever forces caused those cliques to form in the first place. You need representatives from each group. It's a bit like congress, which has similar problems.
And its not just disparate language communities. It's people who want to build influential businesses, and its people who want to insulate themselves against the influence of tech business. Its people who think it's OK to build killer robots, and it's people who don't want to be killed by those robots.
Getting people work together is hard. Nixpkgs tries to do that to such a degree that you can put a version number the result. Maybe it's admirable, maybe it's folly. I think it's both.
I'm not going to blame the people who are ambitious enough to try because as far as I'm aware, whatever other successful communities exist, they're succeeding at a less audacious goal.
Nix governance: still hasn't resolved dependency hell for humans apparently.
This is an almost poetic description of micromanagement. I really like Nix and have been running it as my main OS for several years in the past ~ 10 years.
I don’t think the issues they have are unsolvable, it just appears that the governance model they’re trying to have is not working out, and it’s very difficult to roll back.
Meanwhile, my company is using Nix for everything heavily internally. Everyone gets their dependencies via Nix unless you are like using PAM or something.
Reminds me of Bazel, in the way that it gets adopted by companies with developer support teams (because it solves real problems) but feels frustrating for us ordinary folk. Nixpkgs is kind of a critical part of “ordinary folk” and with the core team disbanding, I feel like my personal moves away from Nix (for projects) are proving correct.
I’m in the process of about to deploy Nixos to server workloads, but am now hesitant because I don’t understand these ramifications.
Personally, I'm sorry and grateful. Sorry that it ended in core folks being burnt out. Grateful since they did some of the most amazing work, more than anyone can imagine two people doing.
1. the "I used nix once/some time ago but I realized it's stupid/hard/whatever"
2. anime pfps/furries/trans/woke are bad
3. complaining about CoC/governance/etc
Irrespective of whatever the posted article is about relating to this technology. This is one of those threads.
Nix seems to have one of the worst discussion quality around here. Rust threads are similar (though they got better recently), specially on the negative unrelated comments side, but seem to have much more engaged people. Maybe Anubis has a similar ratio. I wonder why?
As a layman who has only used AI to package a couple things on NixOS for personal use, I would think that LLM agents are perfect for taking over most of the nixpkgs workflow.
I tell you what. Ever since I migrated my dev workflow to nix package manager (and home manager for system depa), my life became simpler like 10 times
I can configure any macos machine in like 20 mins (I use Determinate)
https://imgflip.com/i/aye90c