I'm really looking forward to 2034, when WebGPU features will catch up to 2024.
By that time, it might even get supported by Chrome for Linux.
On ChromeOS.
WebGPU is now available on Android
51–60 of 75 posts
Re: WebGPU is now available on Android
#52Earlier quoted context omitted.
By that time, it might even get supported by Chrome for Linux.
about:flags in Chromium search for "accel" Disable the blacklist for your GPU.
Which is exactly why WebGL never really took off for games like Flash did, versus native games, or now streaming.
Having drivers installed is not enough as the browser lords decided the computer isn't worthy of playing games.
Re: WebGPU is now available on Android
#53What will be curious about WebGPU getting wider Android deployment is if it results in reducing the effect of variation in the drivers, which very much remain a headache. For example, WebGL type API implementations have had a somewhat flexible idea about data sizes and layout which due to the nature of WebGPU are much less acceptable there. One of the big wins of Vulkan has been that it has levelled the playing field…
It will be same as ever.
The big difference is that on native APIs we can work around them.
On browser APIs, the device gets blacklisted end of story for those folks.
Re: WebGPU is now available on Android
#54>devices running Android 12 and greater powered by Qualcomm and ARM GPUs. So... won't work on any exynos, since they have the AMD RDNA3 arch? Do I get that right?
Hi! I'm the Chrome dev that's been working on WebGPU's Android support. As jsheard said the older exynos devices will work because they're Mali-based. The newer RDNA3-based devices aren't enabled by default simply because our team hasn't been able to sufficiently test on them yet. Same goes for Tegra or PowerVR GPUs. It's entirely a question of spending the time to ensure they're performing as expected (and probably…
First of all thank for the effort.
Secondly, this was a big issue plaguing WebGL adoption, as contrary to native APIs, devices get blacklisted and telling common users to access browser flags is not an option for most products.
Hence why game studios are so keen on streaming instead.
Re: WebGPU is now available on Android
#55What’s the actual utility of this for anyone that isn’t trying to replace native code with web pages? Is this ever going to be worth the no doubt massive investment it required?
It's likely to become the best way to run cross-GPU-platform gpu code in the medium term
That already existed via middleware engines.
Re: WebGPU is now available on Android
#56> Timestamp queries allow WebGPU applications to measure precisely (down to the nanosecond) how much time their GPU commands take to execute compute and render passes > ... > Due to timing attack concerns, timestamp queries are quantized with a resolution of 100 microseconds, which provides a good compromise between precision and security. I don't have a particular need of nanosecond granularity timestamps for WebGPU…
The former is a spec detail (the result is returned in ns) and the latter is an implementation detail (browsers currently quantize the result to 100us). That is a useful distinction since you can use WebGPU outside of the browser by embedding Dawn or wgpu into your own application, and there you should get the maximum resolution the spec allows for. Environments like Electron might also opt-out of that timing attack…
New exciting web fingerprinting vector dropped.
As if we didn’t have a enough already.
Re: WebGPU is now available on Android
#57Re: WebGPU is now available on Android
#58Earlier quoted context omitted.
It's likely to become the best way to run cross-GPU-platform gpu code in the medium term
That already existed via middleware engines.
such as?
Do you mean the clusterfuck that is matching carefully your compiler, ID, hardware, instruction set architecture, incompatible dependency versions, installers, package managers, etc.?
So far, WebGPU was the first and only time that I was able run Stable Diffusion on my own hardware.
Re: WebGPU is now available on Android
#59Earlier quoted context omitted.
That already existed via middleware engines.
such as? Do you mean the clusterfuck that is matching carefully your compiler, ID, hardware, instruction set architecture, incompatible dependency versions, installers, package managers, etc.? So far, WebGPU was the first and only time that I was able run Stable Diffusion on my own hardware. https://websd.mlc.ai/
Unity, Unreal, Ogre3D, Open3D, Godot, Stride, Defold,....
Assuming you want to use 2024 hardware features in 2024.
Re: WebGPU is now available on Android
#60Earlier quoted context omitted.
"trying to replace native code with web pages? " No one wants that. But many like to write their apps only for one plattform - and then still have them run allmost everywhere. The web is the best we have to achieve this. And this will greatly improve the possibilities. Edit: My app will soon finally use no more html elements. It is not a "webpage".
You say no one wants that, then you describe doing exactly that. If your “app” runs in a browser window—a window presented by a browser engine—it’s fundamentally a web page. (They’re two distinct words.)
I .. hate those pedantic discussions. But here you go: a web page by common understanding is mainly something to look at. Page implies document. A web app is a bit more.
(And many tech people hate it, that browsers can do more)
So no, I do not want to replace native code with a web page. But in some cases with web apps.