NixOS is great, but it definitely breaks things. It’s the way it works, though, not whether the software is bleeding edge. Nix lets a package specify its own dependencies, even if those dependencies conflict with those of another package. It does this by breaking the traditional POSIX file system structure that many programs assume they can depend on. It puts all sorts of things where they “don’t belong”, and then uses a small army of environment variables, scripts, and symlinks to stitch it back together so that no individual package realizes what happened. If you only use software from the package manager, this is often (but not always) seemless, but if you download stuff from the web, none of the system libraries it traditionally expects are there. Likewise, if you’re using Nix alongside something like Debian’s apt, I wouldn’t be at all surprised if the two package managers doing things in two different ways causes some issues that are hard to interpret to the uninformed.
NixOS is great, but it definitely breaks things. It’s the way it works, though, not whether the software is bleeding edge. Nix lets a package specify its own dependencies, even if those dependencies conflict with those of another package. It does this by breaking the traditional POSIX file system structure that many programs assume they can depend on. It puts all sorts of things where they “don’t belong”, and then uses a small army of environment variables, scripts, and symlinks to stitch it back together so that no individual package realizes what happened. If you only use software from the package manager, this is often (but not always) seemless, but if you download stuff from the web, none of the system libraries it traditionally expects are there. Likewise, if you’re using Nix alongside something like Debian’s apt, I wouldn’t be at all surprised if the two package managers doing things in two different ways causes some issues that are hard to interpret to the uninformed.