I know this is humor, but for the record this wouldn't work. Each simultaneous TCP connection needs a unique four-tuple (source address, source port, destination address, destination port). If a lot the people behind the NAT try to connect to the same place (destination address and port) at the same time (something popular like Google, YouTube or Netflix), and their source address is the same, the source port needs to be different for each connection. So after at most 65535 connections within a short time the NAT would run out of ports and no one behind the same NAT would be able to open new connections to the same place until the NAT mapping expiries.

So you could have at most tens of thousands of people behind the same NAT, maybe even fewer to make it reliable.

Lossless WebP is still gets way better compression than PNG though, this doesn't change that. Although they mention they're looking to improve it in the next version, so we'll see then.

Still doesn't allow background playback though, so it's useless to me

Mirror's Edge actually had a place with tons of broken glass falling down, where the framerate would drop into the single digits if it used CPU PhysX. I remember that because it shipped with an outdated PhysX library that would run on the CPU even though I had an Nvidia GPU, so I had to delete the game's PhysX library to force it to use the version from the graphics driver, in order to get it to playable performance. If you didn't have an Nvidia driver you would need to disable PhysX for that segment to be playable.

One thing that you do still need root for however is proper backups. The built-in backup system is tied to Google, and it's very limited in what it will back up, nowhere near what you can do with root backup software like Titanium Backup.

The problem is the previous one only has 2G, and the 2G networks will soon be shut down, hence why they're making a 4G version.

And film grain

Expect updates to a lot of things in the near future.

And also a lot of things that remain unpatched for years

And the branchless version may end up being slower on the CPU, because the compiler does a better job optimizing the branching version.

Or are GPUs particularly bad at branches.

Yes. GPUs don't have per-core branching, they have dozens of cores running the same instructions. So if some cores should run the if branch and some run the else branch, all cores in the group will execute both branches, and mask out the one they shouldn't have run. I also think they they don't have the advanced branch prediction CPUs have.

https://en.wikipedia.org/wiki/Single_instruction,_multiple_threads

And supercomputers. And most embedded devices powerful enough to run a full OS.

r/Nofans is now a passive PC cooler subreddit.

That should be a nice complement to r/onlyfans, which has previously refocused to pictures of fans (though it's still private)