NekkoDroid

I'm sorry... should I not be happy when someone that says it is terrible that I own my own RAM has a terrible day???

Better analogy would be "Microwave ovens were never for injecting electromagnetic waves into food. The electromagnetic waves were just a means to heat the food".

Well, the sanest option is to not have the death penalty at all. Anything else is trying to make the problem work.

Changing TREE(2) to TREE(3) is a small change on the input, but a... lets just call it big... change in the output.

Its been a while since I looked further into it, but the individual components were being built with buildstream and I think they were looking to switching the image building to mkosi with buildstream integration (from a quick look at the gnome-build-meta repo it looks like it still didn't happen).

Also a minor nitpick: I wouldn't call Flatpak a/their "dependency manager". It is more like an application manager, closer to winget than a traditional package manager.

Do note that those are en-dashes and not em-dashes.

London according to Google has 9 mil people. So "dozens per person", 9 mil people and 1 mil cameras does not add (or rather multiply) up.

eBPF programs do run at kernel level, but don't have the same full access that a kernel driver would have, they are limited to the APIs that are available for the subsystem they are loaded for. And they can (usually) be unloaded.

The "Does EAC Linux v2 use a kernel driver?" does feel slightly misleading, especially considering the API stability guarantees are also the same as regular kernel drivers, but the "Does EAC Linux v2 run in the background all the time?" doesn't necessarily feel misleading to my understanding.

No, for a system and service management layer.

More like going under a police department post barging about how many criminals they apprehended and reminding everyone the police department killed 5 innocent people in the last week.

On a lot of Android devices you can't install ANY other custom OS because of locked down bootloaders. If you want GrapheneOS specifically that list is even narrower due to 1. official support 2. hardware security features just missing from the devices.

3000 really isn't that much if you think about how much it is used and how relatively extensive it is. Though the 3000 is also not just bugs but also feature requests (only ~800 are marked as bugs and 1.5k are marked as feature requests).

As comparison libarchive is sitting at ~300 open issues and LLVM is sitting at ~30k. Both also being really important in their own ways.