You've probably been there. You install a new program, and suddenly, another one breaks. Or you try to run a project on a friend's computer, and it fails because their setup is slightly different. These problems happen because most systems manage software in a shared, mutable way, like a community kitchen where everyone uses the same pots and pans. If someone changes a pot, it affects everyone's recipe.

Nix is a package manager that takes a different approach. It treats software packages not as messy, shared resources, but as pure, predictable values. Think of it like a mathematical function. If you give the function $f(x) = x + 2$ the input $3$, it will always, without fail, return $5$.

So how does Nix stop packages from interfering with each other? Instead of placing files in shared locations like /bin or /lib, Nix puts every package into its own isolated directory inside a special folder: the Nix store, located at /nix/store.

The name of each package's directory isn't just firefox-125.0. It's a long, unique string of characters generated by a cryptographic hash. This hash is calculated from everything that goes into building the package: the source code, the compiler, all the libraries it depends on, and the build instructions.

If even a single bit changes in any of the inputs, the hash changes, and Nix creates a new, separate directory for the new version. This means you can have many different versions of the same package, or packages with conflicting dependencies, installed on your system at the same time without any issues. They never overwrite each other because they live in different places.

This unique storage method is how Nix solves "dependency hell." That's the classic problem where Project A needs version 1.0 of a library, but Project B needs version 2.0. With traditional package managers, you can often only have one installed, forcing you to choose which project breaks.

With Nix, this isn't a problem. Project A simply gets linked to its required version of the library in the Nix store, and Project B gets linked to its own. They are completely isolated from each other's dependencies. This guarantees that software works predictably and that updates to one package cannot break another.