The Nixpkgs core team has disbanded

Original Article ↗ Hacker News Discussion ↗

The NixOS community is grappling with the abrupt disbanding of the relatively new Nixpkgs core team, highlighting ongoing governance problems and contributor burnout rather than a technical failure of the software itself. Commenters describe years of mounting political and social conflict around moderation, sponsorships, and decision-making structures, with some now questioning the project’s long‑term stability while others stress that Nixpkgs and NixOS continue to function and receive updates. Alongside this, users share mixed experiences of Nix’s power and complexity, debating whether its benefits for reproducible systems and large deployments outweigh the learning curve and ecosystem friction, especially for smaller or solo setups.

Impact of the nixpkgs core team disbanding

  • Core team was small (originally ~4, recently 2) and relatively new (around a year old), not the foundation of nixpkgs.
  • Contributors say nixpkgs and NixOS will continue; the individuals are not stopping their own contributions.
  • Some frame this as a return to the pre-core-team status quo; others see it as another sign of governance strain and contributor burnout.
  • A few commenters claim “NixOS is dying”; others strongly dispute this, pointing to ongoing package and OS updates.

Governance, moderation, and community conflict

  • Many see the root problem as governance: unclear delegation, steering committee “interference” or micromanagement, and heavy process for a volunteer project.
  • Multiple previous crises are cited: a mass resignation of the moderation team, disputes with the steering committee, and other high‑profile resignations.
  • Moderation is portrayed by some as overzealous, politicized, and focused on ideological battles (e.g., over sponsors, “safety”, “fascists”); others blame the steering committee or “systemic” issues that empower bad actors.
  • Several posts attribute the turmoil to broader culture‑war dynamics and “woke” politics; others criticize such framing as oversimplified and divisive.
  • There is consensus that burnout of key contributors is real, even if causes are contested.

Trust in the ecosystem

  • Some users say they stopped using NixOS because repeated drama makes the ecosystem feel unstable and untrustworthy for critical workloads.
  • Others argue governance drama is common in open source, while the technical ecosystem remains “battle-tested” and widely used.

Technical and user‑experience themes

  • Positive experiences:
    • Nix/NixOS praised for reproducible configs, fleet management, robotics deployments, fast and cheap builds, and per‑project environments (often via flakes + direnv).
    • Homelab and company setups report reliable atomic upgrades and easy rollbacks.
  • Negative experiences:
    • Steep learning curve; nix language and nixpkgs described as arcane.
    • Documentation is fragmented, inconsistent (flakes vs non‑flakes, NixOS vs macOS), with many broken links; users rely heavily on chat or LLMs.
    • Package maintenance quality is uneven; some packages missing, out of date, or feature‑reduced, especially on macOS.
    • Some feel Nix is overly complex, operates at the wrong abstraction level, and doesn’t fully solve cross‑platform build pain.

Flakes and “experimental” status

  • Flakes are widely adopted in practice; several argue they must be declared officially supported instead of “experimental.”
  • Others note real drawbacks (e.g., copying large local data into the store on nix run .#...).

Ecosystem, funding, and alternatives

  • Question raised whether companies heavily relying on Nix should fund its development; replies range from “they should” (to reduce burnout) to “that’s not owed under open source norms.”
  • Some users move to or recommend alternatives: Guix, Kubernetes-based setups, immutable Fedora variants (like Bazzite/Silverblue), or newer systems such as StageX; others use NixOS to host Kubernetes instead.
  • A few suggest Nix’s model is so compelling that, even if the current community implodes, someone else will pick up the ideas.

Meta: community culture and discussion quality

  • Several note repeated Nix threads devolve into the same pattern: “I tried Nix and quit,” culture‑war fights, and complaints about governance, regardless of the original topic.
  • Cultural observations (anime avatars, furries, queer identities, defense‑industry users) are tossed around, sometimes playfully, sometimes derisively.
  • Some contributors explicitly avoid Discourse/“community” spaces due to drama but continue contributing PRs directly to nixpkgs.