I realize that Gentoo became a meme at some point, but it also seems that it might have transcended to the level of infrastructure. Thus, you rarely ever heard about it for the same reason you don't hear people talk about hammers -- it is doing its job running tens (hundreds?) of millions of chrome books among other things.
No flare, nothing fancy, it has solved a whole bunch of packaging, deployment, and environment control problems and gotten out of the way of its users (mostly ... chuckle), and it did it all with a pile of bash scripts and a little python here and there. Want to use systemd because you have a use case that would benefit from it? Go right ahead! The engineering work is done, no need for fights on the mailing list. Don't want to use systemd? `eudev` to the rescue! There are sound engineering reasons for not using systemd while also wanting to use some other (seemingly) completely unrelated piece of software that just happens to have a dependency on the kitchen sink.
Despite being a rolling release distribution, I find that the UX and workflows are more stable over long periods of time than any of the more popular LTS style distros. When I started fiddling with Ubuntu so that I could help my colleagues debug issues it took me an embarrassingly long time to realize that there isn't really such a thing as Ubuntu, just 14.04, 16.04, 18.04, etc. Each is some different form the other that stack overflow questions from one LTS are often simply wrong for another.
Writing this I wonder whether rolling release distros aren't effectively the original form of chaos engineering -- if everything is going to be changing all the time then it forces the developers to solve a different and perhaps more fundamental set of problems and ultimately leads to greater stability in the long run.
The Nix thesis[0] explicitly cites Gentoo multiple times; it's very much inspired by, and intended to surpass, Gentoo.
0. https://gitweb.gentoo.org/repo/proj/prefix.git/plain/scripts...
I assume you're referring to the following sentence, but that's not what it's talking about.
>As claimed in the introduction, deployment systems tend to have monolithic trust models. Typical Unix package management systems such as RPM [62], Debian APT, or Gentoo Linux [77] allow installation of software by the administrator only; software installed by individual users is not managed by those tools
This is talking about a single instance of the package manager; for any given instance of the package manager (where an "instance" is defined by various things like the list of installed packages, package data, various package management databases, etc.), only the owner of that instance is allowed to install new packages. For a system-wide package manager, only root is (safely) allowed to install new packages.
Even at the time, RPM and dpkg, and presumably portage, had the ability to create non-system-wide instances of the package manager, like Gentoo Prefix does; but even for such instances of the package manager, it's only safe for the owner to install new packages. (You wouldn't want random other users installing packages in your home directory!) Such instances don't share anything with the system-wide instance - it's essentially like creating a chroot or container.
The reason this is being pointed out in the thesis is that Nix does not have this limitation; any user can safely install arbitrary packages into the system package manager, which are visible to the system, share package data, etc.
I'm taking pains to be clear about this because, IMO, this is one of the places where Nix has the clearest advantage over traditional package managers.
Who hasn't heard of, and even know the elevator pitch for Gentoo? For decades already no less.
It's great, and it obviously qualifies to be in the full list, but it's not interesting or novel to anyone who already uses unix-like os's other than osx.
1 - Can we name our distro Void.
2 - Why?
1 - Since it devoids of systemd