There's a lot of literature about font rendering predating compute shaders too, compute shaders are not a functional prerequisite by any means.

Here's eg one case: https://github.com/astiopin/webgl_fonts

Yeah, that as well.

WebGL 2.0 is kind of PlayStation 3 like in capabilities, that we seldom see that in action besides shadertoy, Google Maps/Earth, and 360° views on ecommerce sites is another matter.

Yes, I also don't understand why google abandon webgl compute shader, just because webgpu will have same, so they force developer using newer api.

Interesting. Do you have any more context around this? It sounds uncharacteristic of Google to do so given their usual stance on browsers being all things to all people.

Yes,

https://registry.khronos.org/webgl/specs/latest/2.0-compute/

https://github.com/9ballsyndrome/WebGL_Compute_shader

And then Google decides not implementating it after all, because of WebGPU.

https://github.com/9ballsyndrome/WebGL_Compute_shader/issues...