[mschuetz]

I'm really looking forward to 2034, when WebGPU features will catch up to 2024.

[vetinari]

By that time, it might even get supported by Chrome for Linux.

[bhouston]

Why is linux supporting taking a while? I figured the underlying graphics subsystem on Android is Vulcan right? Wouldn't that also be the main graphics subsystem on Linux these days?

[reactordev]

You know we’ll have all moved onto Romulan by then, leaving Vulkan and Metal behind - including WebGPU.

In seriousness though, WebGPU in Chrome with “non-free” Linux GPU drivers should work, no?

Edit: I see it’s still behind a flag

[anthk]

about:flags in Chromium

search for "accel"

Disable the blacklist for your GPU.

[pjmlp]

On ChromeOS.

[bmitc]

What features?

[jms55]

Personally, the ones I'm most looking forward to:

* Subgroup operations

* Push constants (available in wgpu, but not WebGPU the spec/web impl)

* u64 + atomic image ops

* Mesh shaders

* Raytracing

* Binding arrays / descriptor indexing + device buffer addresses

[pjmlp]

Looking back to 10 years long WebGL adoption, and WebGPU being based on 2015 features, that is pretty much spot on.

[2OEH8eoCRo0]

In 2034 it'll be as dead as Flash because of security issues.

[mschuetz]

Not really, that is not the problem of WebGPU. The worst you can do is crash the tab. With an unstable graphics driver, there might even be the option to crash the system but that's hardly a security issue, only an annoyance.