HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NixOS
nix
C++2014–2026
NixOS / nix

nix

Nix, the purely functional package manager

94Distinct people
133Mentions
0Explicit recommenders
18KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Nix, the purely functional package manager

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:59:04 AM UTC.

Mentions over time

HN mentions by year133 dated mentions

Observed mentions: 2014-10-11 22:08:41 UTC to 2026-09-26 16:52:12 UTC.

01020302014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 21 mentions; 0 submissions, 21 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 26 mentions; 0 submissions, 26 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 21 mentions; 1 submissions, 20 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 17 mentions; 1 submissions, 16 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC404
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC927
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC707
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC21021
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC11110
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC26026
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC21120
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC17116
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC909
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC312

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Nix Nix is a powerful package manager for Linux and other Unix systems that makes package management reliable and reproducible. Please refer to the Nix manual for more details. Installation and first steps Visit nix.dev for installation instructions and beginner tutorials. Full reference documentation can be found in the Nix manual. Building and developing Follow instructions in the Nix reference manual to set up a development environment and build Nix from source. Contributing Check the contributing guide if you want to get involved with developing Nix. Additional resources Nix was created by Eelco Dolstra and developed as the subject of his PhD thesis The Purely Functional Software Deployment Model, published 2006. Today, a world-wide developer community contributes to Nix and the ecosystem that has grown around it. The Nix, Nixpkgs, NixOS Community on nixos.org Official documentation on nix.dev Nixpkgs is the largest, most up-to-date free software repository in the world NixOS is a Linux distribution that can be configured fully declaratively Discourse Matrix: #users:nixos.org for user support and #nix-dev:nixos.org for development License Nix is released under the LGPL v2.1.
Read the full README on GitHub

What Hacker News says

11 sources
I don't know much about Nix, although it has been on my radar for some time. The claim that the language performance is bad pops up time and again, and I'm sure many people would be happy to have a faster alternative --- so props to them for trying to address this clearly important problem. That being said, in perusing related issues on GitHub such as [1], I have found no serious attempts to even profile the damn thing. The typical attempt seems to be throwing a random idea at the evaluator and crossing fingers. The example of a "performance experiment" [2] from the article is self-described as follows: > Add an alternative impl of the now-abstract Bindings base class that is backed by a std::vector, somewhat similar but stylistically a little superior to the array-backed implementation in upstream nix. I fail to see how that is a perf
Read the rest
ormance experiment when it does not mention performance at all. The post also mentions issues with the general Nix design and a desire to modernize it, which I am unqualified to comment on, but seems a worthwhile endeavor in and of itself. I do hope that they won't end up writing a new evaluator for the Nix language without a proper understanding of what makes the current one slow and a clear plan not to repeat its mistakes, or the new one risks being just as slow as the old one. [1] : https://github.com/NixOS/nix/issues/2652 [2] : https://cl.tvl.fyi/c/depot/+/1123/
In Tvix: We Are Rewriting Nix
There are a couple issues tracking FreeBSD support for Nix [0,1], the package manager indicating it works there. Depending on the level of integration you want that might be sufficient, that would already be enough to generate the system config files for example, but to get the sort of integration you get on NixOS with different generations and the ability to rollback at boot would require more work. This would look something more like nix-darwin [2] than NixOS really. I wouldn't be entirely surprised if OpenBSD works too, I might spin up a VM and see... [0] https://github.com/NixOS/nix/issues/3280 [1] https://github.com/NixOS/nixpkgs/pull/81459 [2] https://github.com/LnL7/nix-darwin
In OpenBSD 7.0
There are multiple ways of doing it. The obvious one (updating nixpkgs) you already mentioned. Second way is to override[1], in documentation they are showing how to change compilation parameters, but you can also use this to change version of dependencies or source tarball for the package. As you use Nix you will eventually need to do it as sometimes package was not updated, or perhaps you need to use older version, or enable compilation option. Third way is to use overlay[2]. In previous way an existing package was modified. Overlay allows to completely replace or add a new one. For example there is a tool called poetry2nix[3], which on the fly translates python poetry lock file to Nix so nix can build them. Nixpkgs includes it and generally is frequently updated, but maybe there was a fix yesterday that hadn't made it there yet and it
Read the rest
fixes an important bug. You can fetch that repo independently and attach it to nixpkgs (or you can use it directly). Nix also has upcoming feature flakes which to my understanding takes this to a new level. So you can easily compose multiple repos like this in your application. > Theres clearly more to Nix than just setting up language environments, which I'm guessing is where its usefuleness really kicks in. But purely for lang env set up, I'm not sure I see a point over other tooling... I use it this way and the killer feature for myself is that for a project all I need to have installed is Nix and I can have exact environment the dev used. It's not mentioned often, but I think a demo of it would be the repo for Nix program[4]. Typically when you want to compile some open source program, after you check out the repo, a hunt starts for the building tools and libraries needed. With nix you just issue build command or enter build shell[5] and things just work with no errors (or at least I did not get them when trying it a while ago. Everything worked on first try). [1] https://nixos.org/manual/nixpkgs/stable/#chap-overrides [2] https://nixos.org/manual/nixpkgs/stable/#chap-overlays [3] https://github.com/nix-community/poetry2nix [4] https://github.com/nixos/nix [5] https://hydra.nixos.org/build/153568733/download/1/manual/co...
In Ditch your version manager
No progress on a nix-windows recently. I think the hardest part has just been keeping up with nix when we need to rewrite the build system. However, https://github.com/NixOS/nix/pull/3160 to switch to Meson, has gotten new life breathed into it. Pamplemousse, who is interning where Edolstra works, is fuzzing Nix and needs Meson to make that less burdensome. If that does get merged, than nix-windows can just be about Windows and not also be about Nix's build system, which will make it a lot easier to finish.
In Valve Steam Deck
I've been using nix on macOS as my primary package manager for years. Really love it! Specifically nix-shell is a blessing a you can quickly try out things without worrying about breaking some other packages on the system. Initially we've only used nix for development at my company, but now we're also running most of our servers with NixOS. This allows us to use our dev package definitions in production, so our dependencies are always in sync between dev and prod. I've written a blog post about all the advantages we get with nix in our framework IHP a while ago, if you're curious, check it out: https://ihp.digitallyinduced.com/blog/2020-07-22-why-ihp-is-... If you're using an older mac and have troubles with installing nix, try out the new installer in this GH issue: https://github.com/NixOS/nix/pull/4289 (the command is in the "Try it ou
Read the rest
t" section). It's already merged, but not released yet. So far this has solved all the issues on older macs for me. Also check out https://nix.dev/ which has many great resources to get started :)
In macOS Nix setup: an alternative to Homebrew (2020)
Yep. The advantage of `with` is that we're dealing with first-class values (attribute sets, like `{ foo = "bar"; }`), rather than an implicit environment/context. My rationale is at https://github.com/NixOS/nix/issues/1361#issuecomment-390420... The thing about shadowing is that `with` will not shadow anything that's in the implicit context, which includes things defined by `let` (hence why I avoid it) and function arguments (unavoidable). We can shadow other `with` bindings as much as we like, e.g. with { foo = 1; }; with { foo = 2; }; with { foo = 3; }; with { bar = with { foo = 4; }; foo; }; [ foo bar ] This evaluates to [ 3 4 ], since later bindings to `foo` will shadow/override earlier ones. This doesn't work for bindings that are in the implicit environment/context, for example: with { f = foo: with {
Read the rest
foo = 42; }; foo; }; f 123 This evaluates to 123, since the binding `with { foo = 42; }; ...` doesn't shadow/override the argument `foo`. The rationale for this behaviour is to avoid changes made to an attrset from overriding explicit arguments. For example: foo: with bar; x + foo This is presumably meant to behave like `foo: bar.x + foo`, but a future change to `bar` might include a `bar.foo` attribute, in which case we don't want the above to change behaviour to `foo: bar.x + bar.foo`. I understand this rationale, especially when using huge, constantly-changing attrsets like `with nixpkgs; ...`, but it's still annoying ;)
In Nix is the ultimate DevOps toolkit

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.