I never understood why they targetted low end hardware with a tech stack that's notoriously slow (web).
I never understood why they targetted low end hardware with a tech stack that's notoriously slow (web).
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.
Then use something more efficient than the web stack. In the end, Android ran better on the same devices and had better software support.
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.
VRR only works on Xorg if you only have 1 screen. And XWayland is broken on Nvidia.
I know. Too bad that Nvidia has more than 85% of marketshare.
4500 in CSGO in 9 years and I'm not planning to stop any time soon.
Yes but nobody wants to invest that much time into building something that only works when rooted.
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.
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.
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.
Can you please elaborate?
Background process limits, blocked system calls, apps getting killed for using too much memory, Android power governor bullshit,...
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.
This relies on Google servers anyway.
As long as the tracking is purely local, this seems like a good solution to me.
I don't think that's a thing in Europe.