Distro-hopping is a valid hobby, but it's not for everyone. If you aren't specifically interested in distros and fiddling with packages, hopping around on your "daily driver" can be disruptive. If you just want something that works, there's nothing wrong with figuring out which distros do what you need and using one of those for work and play. If something catastrophic happens to a distro to make it literally unusable, you can worry about that when it happens. There is usually something else which is almost the same. Few people will get much value from hopping between distros which are basically the same, just because the distros are put out by different companies or install different packages by default.

The post volume is still much lower, but that isn't all bad, since the toxicity and quality isn't as bad and unlimited scroll time isn't healthy.

"There are no Linux gamers. It's useless"

"Wow, look at all the Steam Deck users!!"

It's the same logic they're still using: they want to monetize Reddit more aggressively, even if that kills its appeal and they have to brutalize their own community to do it.

They fired Victoria because they were trying to aggressively monetize IAmAs in ways that were going to fuck community interests, and Victoria pushed back. Think Rampart, except companies can pay to ensure that it doesn't become a PR fiasco, so it's guaranteed astroturf.

Reddit has been classy ever since.

The mob boss who wants $8/mo for a lame service but won't harm you if you don't want it?

How about affordable housing?

Twitter was already shit under Dorsey.

More than one issue matters.

You're right - having multiple copies of everything is a drawback of housing each application in its own container or VM. The standard rejoinder is that disk space is cheap. The validity of that rejoinder depends on what you're doing and what hardware or budget you are working with.

Another problem is that old versions of these dependencies will be baked into an image that is then used for many years without updates. This ensures the application keeps working without being disrupted by an update to a shared library, but it also means things like security flaws persist. Arguably, this is mitigated by only that image having the problem, but one insecure app can be a real problem - especially when it accesses shared resources - and when the same problem applies to many applications.

Compiled code optimized for a specific system's hardware is less relevant than it used to be - even Gentoo users do not focus on this anymore. Rolling your own container isn't much harder than compiling with your own options.