Oh sure, I completely agree. But a clear trail of custody around all of the text segments that end up in the binaries that get executed serve both use cases wel

Oh sure, I completely agree. But a clear trail of custody around all of the text segments that end up in the binaries that get executed serve both use cases well. I appreciate that for a lot of desktop users they just want it to work and aren't terribly picky about which minor version of `libfoo` is required to get Firefox or Chrome to start. But there are vendors and maintainers who are deeply concerned about such things when attempting to give the desktop user a seamless experience, and why a big mushy puddle of who-friggin-knows code makes that job any easier? Who friggin knows. I think it's just inertia. The fact of the matter is that everything from snaps to flatpaks to docker to this whole containerization craze is mainly dealing with the pick a card, any card outcome you get with a bunch of random `.so` in `/usr/lib/`.