Avid NixOSer here. While it's sad, that we're not there yet in terms of user-friendliness, I still think, given the radical approach, NixOS takes, it's increadi

Avid NixOSer here. While it's sad, that we're not there yet in terms of user-friendliness, I still think, given the radical approach, NixOS takes, it's increadibly feature-complete. I find it easy to tweak, too, but that might be due to previous experience with functional systems. For the specific suggestions in the article, I'm not convinced that they are possible, while retaining the same benefits: - Filesystem snapshots are not enough to deal with, e.g. slightly different builds of the same shared library - Namespaces, however are. In fact, there is buildFHSEnv in nixos, to take advantage of those. - Hiding of runtime dependencies is done with the intent to minimize "accidental success", because that leads to unstable systems. - Also a package could, e.g. depend on a patched version of Python2.7, that you'd never want to accidentally end up on the system path. Having packaged some, I do feel the author's pain though. I wonder, if we couldn't get rid of a lot of upstream grind, by encouraging usage of fhs-env namespaces.