> we rarely see exploits I can't think of an analogy that doesn't come off crass. I posit the likelihood the morass that is webgpu not having exploitable bug

> we rarely see exploits I can't think of an analogy that doesn't come off crass. I posit the likelihood the morass that is webgpu not having exploitable bugs approaches 0 approximately 25 seconds after the first public release of the code, if not months prior. Its only when one of two things occur that publishing happens, basically: intelligent frustration, and "for the lols". Someone hits a bug and gets pissed that the authors of the libraries blame everyone but the library authors. When working around the bug discover its not just a bug. Warn devs. Sometimes responsible disclosure means a quiet fix and then disclosure, but usually it means "here's the exploit they don't care ig" If there's not enough curious people poking things, exploitable stuff could remain hidden too long.