6 ms·

I've been wondering for a long time when we might expect to see a stable WebGPU API in all major browsers (mostly concerned with my daily browser, Firefox), so

I've been wondering for a long time when we might expect to see a stable WebGPU API in all major browsers (mostly concerned with my daily browser, Firefox), so I've been looking for an official message on the topic. Deno claims the spec is ready > The [WebGPU] spec has been finalized but the official WebGPU spec [1] still describes it as a draft. Have I misinterpreted something here or is there some missing context around Deno's statement? [1]: https://www.w3.org/TR/webgpu/ https://www.w3.org/TR/webgpu/

flohofwoe 3y ago
This might be a better page to get an idea what's the status in different browsers: https://github.com/gpuweb/gpuweb/wiki/Implementation-Status https://github.com/gpuweb/gpuweb/wiki/Implementation-Status
fulafel 3y ago
There seem to be no current 1.0 discussions yet on the GitHub prpject, seems possible it's a mistake at the Deno end.
FL33TW00D 3y ago
If you're using any Chromium based browser it's on your machine right now.
- edflsafoiewq 3y ago
  The question is, is it still going to change?
  - flohofwoe 3y ago
    Minor things probably yes (for instance check the "What's new in WebGPU (Chrome xxx)" articles here: https://developer.chrome.com/docs/web-platform/webgpu https://developer.chrome.com/docs/web-platform/webgpu), breaking changes probably not.
Jasper_ 3y ago
In the W3C process, in order for a TR to upgrade from a Draft to a finished specification, it needs two shipping implementations. Firefox and Safari are both working on theirs. We hope the only changes involved in this process will be minor and/or editorial. Once a second implementation ships, it will move out of draft.