“There's the factor of how soon does it get into Nix packages, and then there's how soon is it actually on your machine. Nix is often one of the fastest to actually get it patched in the code. But because of the way Nix works, it can sometimes be one of the slower ones to actually get it on your machine… You can think of Nix packages as a giant tree that all depends on each other. If you're just doing a leaf of that tree, it's not a big deal. But if you're doing something that's really at the root of that tree, you have to rebuild everything under it.”

the factor of how soon does it get into Nix packages? And then there's how soon is it actually on your machine? And this is where it sort of bifurcates because Nix is often one of the fastest to actually get it patched in the code. But because of the way Nix works, it can sometimes be one of the slower ones to actually get it on your machine because that whole reproducibility and like you can think of it, Nix packages as a giant tree that all depends on each other. And so if you're just doing a leaf of that tree, it's not a big deal, right? It's just one. You know, a package, maybe a couple of libraries related to it that you have to rebuild. But if you're doing something that's really at the root of that tree, you have to rebuild everything under it.