That's a wgpu-specific extension, not part of the actual WebGPU spec, so you can't use it on the web.

https://github.com/gpuweb/gpuweb/blob/main/proposals/subgrou...

There is a proposal for supporting subgroups in WebGPU proper but it's still in the draft stage.

I'm aware. It is an implementation of the linked proposal.

The `wgpu` implementation linked will make its way into Firefox eventually. Dawn will follow up with a similar one for Chrome.

I was linking it to demonstrate there are no technical hurdles and it's only really approval remaining.

Ok, but that's not what "landing" means.

Native extensions unusable on Web browsers don't count.

Then nothing involving WebGPU counts since it's not implemented on other browsers than Chromium and not on Linux even in Chromium…

WebGPU is brand new, and the paint is still wet. It doesn't make sense to dismiss things that haven't landed in browsers yet as “unusable on the web”.

There’s an advanced setting in Safari to enable it, but I can’t say how well it works. In this instance it doesn’t.

It doesn't work at all. Doesn't even exist in Safari anymore because they ditched the old implementation and are rewriting everything.

Multiple engineers are working on adding it back: https://github.com/WebKit/WebKit/pulls?q=is%3Apr+is%3Aclosed...

It is a WIP web standard. And the spec is still evolving most things are stable at that points, but new features are still being added, like this one!).

And that's how the web works, it was the same for WebRTC which spent 2-3 years in such a state, same for MSE, etc.