We do for some elements of our pipeline. WebGPU will give us more opporunity for this in the future too but right now we need broader device support unfortunately.

Sure, but that's much more complex to implement, and comes with its own overhead.

Not that WASM tooling is such an example of great developer experience.

It's much easier to integrate some Wasm than it is to rearchitect your software to run on a GPU.

Or you could use Wasm

WASM is slower, and the toolchain sucks for most languages.

Why does "most" matter in this case wnen you just need 1 that suits your needs?

> WASM is slower […]

Without more details on their exact use case, their algorithms, and their data movement patterns, you have no way of knowing this. Doing stuff on the GPU isn't automatically faster than doing it on the CPU.