K0bin

As long as the tracking is purely local, this seems like a good solution to me.

This relies on Google servers anyway.

Encode/Decode has nothing to do with the GPU

They compile Java Bytecode to Dalvik Bytecode and run that on the Android Runtime which is a tiered JIT compiler.

It still inherits the issues of Java such as the GC, no stack allocated value types, poor cache locality, etc. Although tbf the GC on Android is pretty fucking good these days and doesn't pause the world anymore.

I know. Too bad that Nvidia has more than 85% of marketshare.

VRR only works on Xorg if you only have 1 screen. And XWayland is broken on Nvidia.

For one viewport!

The problem with Series S is split screen.

Also that's 6GB of dedicated VRAM. Consoles have unified memory, so you need to fit the OS and the non-graphics memory in there too.

When I read the headline I thought it meant it was also not viable for PCs either, which doesn't seem to be the case at all. Most PCs have at least 16GB ram these days.

Also keep in mind that PC doesn't have unified memory. So there's usually at least 8GB of VRAM in addition to whatever amount of main memory you have.

Yes but nobody wants to invest that much time into building something that only works when rooted.

The purpose of it is to move controls down to the bottom and make it reachable. If there's enough content, you still get to use the entire screen real estate by just scrolling a bit.

I don't think that's a thing in Europe.

Can you please elaborate?

Background process limits, blocked system calls, apps getting killed for using too much memory, Android power governor bullshit,...