Live data from Hacker News

Chrome ships WebGPU

developer.chrome.com

11–20 of 405 posts

Re: Chrome ships WebGPU

#15
I lost all hope for WebGPU after they decided to roll their own ad-hoc shader language that kinda looks like, but is totally not rust.

At least with WebGL you had C.

Without SPIR-V support this spec is just another tire on the fire that is the modern web.

Re: Chrome ships WebGPU

#16
post #12

I think Firefox aims to have this in Firefox 113, WebGPU was just enabled by default in nightly last week. https://bugzilla.mozilla.org/show_bug.cgi?id=1746245

"Firefox's implementation is based on the wgpu Rust crate, which is developed on GitHub and widely used outside Firefox."

Re: Chrome ships WebGPU

#18

In case you confused this with webgl as I did: > WebGPU is a new API for the web, which exposes modern hardware capabilities and allows rendering and computation operations on a GPU, similar to Direct3D 12, Metal, and Vulkan. Unlike the WebGL family of APIs, WebGPU offers access to more advanced GPU features and provides first-class support for general computations on the GPU.

And to prevent device fingerprinting, all the operations are specified to deterministically produce the same bit-exact results on all hardware, and the feature set is fixed without any support for extensions, right? Or is this yet another information leak anti-feature that we need to disable?

I'm afraid it's the latter: https://gpuweb.github.io/gpuweb/#privacy-considerations

Re: Chrome ships WebGPU

#20

In case you confused this with webgl as I did: > WebGPU is a new API for the web, which exposes modern hardware capabilities and allows rendering and computation operations on a GPU, similar to Direct3D 12, Metal, and Vulkan. Unlike the WebGL family of APIs, WebGPU offers access to more advanced GPU features and provides first-class support for general computations on the GPU.

And to prevent device fingerprinting, all the operations are specified to deterministically produce the same bit-exact results on all hardware, and the feature set is fixed without any support for extensions, right? Or is this yet another information leak anti-feature that we need to disable?

Someone mean would say that this is not a bug, but a feature for the people who are paying for Chrome.
Post reply on HN