# Nixpkgs 38 Hacker News commenters recommended Nixpkgs and 22 criticized it, November 2025 to November 2026. It was recommended in 11 of 13 months. **Verdict:** Huge, up-to-date package collection with git-tracked history and maintainer-reviewed changes; critics say its tangled, organic complexity makes unstable branches and packages break or go stale. ## Why people recommend it - Largest up-to-date package collection (6 comments): "Nixpkgs definitely appears to be the largest and most up-to-date single Linux package repository out there." ([source](https://news.ycombinator.com/item?id=49503183)) "One strength of nixpkgs that probably appeals to Arch users too is how much software is available" ([source](https://news.ycombinator.com/item?id=50167719)) "Nixpkgs is the largest package repository across distros by volume" ([source](https://news.ycombinator.com/item?id=49218892)) - Git-backed history and tracking (5 comments): "the issues given for nixpkgs are actually demonstrating the success of using git as the database" ([source](https://news.ycombinator.com/item?id=46395022)) "nixpkgs and nix-commands integration with git works quite well and is not an issue" ([source](https://news.ycombinator.com/item?id=46391999)) "Nixpkgs wouldn't have been as successful if it hadn't been using Git" ([source](https://news.ycombinator.com/item?id=46393701)) - Easy to navigate monorepo (3 comments): "nixpkgs being a monorepo makes it even better. The code is surprisingly easy to navigate and learn if you've worked in large codebases before" ([source](https://news.ycombinator.com/item?id=46398350)) "Nixpkgs is pretty well organized and I find navigating it not that hard once you read the packaging guidelines." ([source](https://news.ycombinator.com/item?id=46366371)) "I remain an advocate for the huge monorepo of build recipes." ([source](https://news.ycombinator.com/item?id=46395339)) - Changes reviewed by maintainers (3 comments): "a pretty comprehensive monorepo of packages with a more normal review process than the AUR" ([source](https://news.ycombinator.com/item?id=48607228)) "it still operates at an absurd scale and yet has a higher bar to infiltration with malware" ([source](https://news.ycombinator.com/item?id=48613935)) "the changes that end up in nixpkgs are all reviewed by maintainers" ([source](https://news.ycombinator.com/item?id=49146921)) ## What people warn about - Tangled, organic complexity across packages (4 comments): "as soon as you opt into one part of nixpkgs you end up implicitly opting into large parts of it because of common code in nixpkgs" ([source](https://news.ycombinator.com/item?id=49857770)) "This has a lot of organic complexity to it, coming from multiple contributors, with competing ideas for achieving results." ([source](https://news.ycombinator.com/item?id=50065639)) "a lot of the complexity when dealing with Nix is with the large and organic complexity of nixpkgs" ([source](https://news.ycombinator.com/item?id=46471315)) - Packages often broken, abandoned or outdated (4 comments): "your configuration is all tied to whether the entirety of nixpkgs-unstable is working can be a real headache" ([source](https://news.ycombinator.com/item?id=46464761)) "half of the technologies grandparent listed are either missing entirely or in a hilariously broken state" ([source](https://news.ycombinator.com/item?id=47480086)) "I think nixpkgs are a bit overhyped; I've encountered many packages that are abandoned and outdated." ([source](https://news.ycombinator.com/item?id=47490321)) - Slow compiles and large downloads (3 comments): "I've embraced daily shallow clone/fetches and the burden is now mostly just the 2GB of disk space." ([source](https://news.ycombinator.com/item?id=46837702)) "nixpkgs maintainers are hardline purists it takes 15 minutes to compile from source" ([source](https://news.ycombinator.com/item?id=45908755)) "that's already more or less what you want, except even the tarball is 46 MB" ([source](https://news.ycombinator.com/item?id=46393019)) - Weak review; self-merging possible (2 comments): "Anyone with contributor rights can make a fake identity, make a PR with it, then merge their own PR." ([source](https://news.ycombinator.com/item?id=48146749)) "due to the huge PITA it was to find someone with contributor rights to sign off on it" ([source](https://news.ycombinator.com/item?id=48122900)) ## Alternatives hackers recommend - [Arch User Repository](https://hackerapproved.com/p/arch-user-repository.md): 34 recommend - [Arch User Repository](https://hackerapproved.com/p/aur.md): 20 recommend - [crates.io](https://hackerapproved.com/p/crates-io.md): 17 recommend - [PyPI](https://hackerapproved.com/p/pypi.md): 16 recommend - [CPAN](https://hackerapproved.com/p/cpan.md): 13 recommend ## Cite as Hacker Approved, "Nixpkgs", https://hackerapproved.com/p/nixpkgs/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).