imecth

Idk how to explain, corpses in Fallout never despawn. That item you hid in the bush? it's still there 300h later. It has a certain persistence that isn't that common.

That's not necessarily a good thing world building wise, I'd certainly expect bodies to eventually get eaten / buried / rot for example.

The former, there's this freenode article that elaborates as for why this is happening.

Teenagers might have done 1 supermarket, this isn't a prank - it's an attack.

I mean setting the OOM killer not to crash your desktop is a good start (which is what ubuntu is doing), but beyond that there's not much you can do because there's no such thing as a safe process to kill.

IDK how early OOM killer isn't standard for desktop distros.

I'd wager it's because randomly killing processes can create data loss, that makes it a dangerous behavior to default to.

Seriously, the article doesn't say after 2 pages.

it's here, and yes it's gnome vs kde but the different distro muddies the comparison.

why comment?

Because the concept that there's a sweet spot where motorcycles are danger free is asinine, even if you, the driver make 0 mistakes (as if) you're much more vulnerable on a motorcycle to other people's mistakes.

Those that (can and do) continue become super aware of their surroundings and are mostly the safest drivers out there, and the death and accident rate goes way down.

That's a hella cope, just admit you like the danger and embrace it.

not pay anything forever

Things aren't that simple, included in the microsoft licensing price are things like customer support - and not just for windows but other products like office, and none of that are part of the 0$ linux license. If you want customer support on linux (redhat, canonical...) it ain't free either.

Getting an old package will work for a while, but sooner or later dependencies will start to break and then you'll be back to square 1. At that point you'll need to rebuild it, and when that fails you'll need to start adding patches... and this is just one package. there's an increasing amount of slop in linux, including the kernel itself, i'm afraid if you have a purist attitude you're gonna want to start looking at other projects like freebsd.

Extensions rewrite the shell's code, they're both very powerful and dangerous, it's why they're all reviewed by GNOME devs. I'm not sure letting people optionally bork their shell is a good idea, even if there's some automatic recovery options and it's gonna be harmless most of the time. No, the correct solution is if you like the extension you pick up the mantle, it's all open source - you can ask for the keys or fork away.

The purpose of this is to force extension developers to verify that their extension works on the new version. The alternative would be extensions randomly breaking your system on upgrade.