VRR only works on Xorg if you only have 1 screen. And XWayland is broken on Nvidia.
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.
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.
If an OCed Nintendo switch is capable of this then I'm pretty sure it is technically possible to get cyberpunk 2077 running in a playable state
It's only possible because Qualcomm designs their GPUs to support D3D12 because of their Windows laptop ambitions. No current Mali GPU, no matter how fast on paper, will ever run Cyberpunk. The feature set is simply not there.
You're also ignoring Android limitations.
Super, auf genau so einen Kommentar hab ich gehofft!
Außerdem finde ich persönlich den Vergleich mit anderen Quatsch. Jeder Tote ist einer zu viel
Natürlich, trotzdem finde ich die Statistik interessant.
Das ist genau das Gleiche wie wenn die Bank sagt man kann nur von der App aufs Banking zugreifen weil der Browser wäre ja so unsicher. Das
Aber wehe, du entsperrst den Bootloader und installierst ne third Party Androidversion. Das wäre auch unsicher! Bleib schön bei deinem 3 Jahre alten Betriebssystem mit haufenweise bekannten Exploits.
Regular Wine doesn't even handle system calls. It reimplements the Windows user space.
Cassia will use FEX for x86 emulation and the goal is to run the Wine libraries (and DXVK) as ARM64.
Cyberpunk is obviously not feasible. It might run on phones with a Qualcomm SOC and lots of memory but it's not gonna be playable.
Then use something more efficient than the web stack. In the end, Android ran better on the same devices and had better software support.
I never understood why they targetted low end hardware with a tech stack that's notoriously slow (web).
view more: next ›
K0bin
joined 1 year ago
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.