2 ms·

I track population frequency of WebGPU extensions/limits here: https://web3dsurvey.com https://web3dsurvey.com. The situation currently is much better when Web

I track population frequency of WebGPU extensions/limits here: https://web3dsurvey.com https://web3dsurvey.com. The situation currently is much better when WebGL1/WebGL2 but there is still a lot of surface area.

codedokode 4y ago
Interesting. The data shows that WEBGL_debug_rendered_info [1] which allows sites to know the name of your graphic card, is supported almost in 100% of browsers. Seems that better fingerprinting support is really a priority among all browser vendors. [1] https://web3dsurvey.com/webgl/extensions/WEBGL_debug_renderer_info https://web3dsurvey.com/webgl/extensions/WEBGL_debug_rendere...
- kevingadd 4y ago
  This is sadly a requirement for the time-honored game development tradition of "work around all the bugs in end user drivers", which also applied to WebGL while it was still immature. At this point there's probably no excuse for continuing to expose that info though, since everyone* just uses ANGLE or intentionally offers a bad experience anyway.