Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem is security, as usual. You can use opengl to exploit a host system, therefore all interactions have to be whitelisted and checked. Compute shaders I know can be crafted to bring your PC to a grinding halt.

Webgpu will be a lovely security nightmare. The underlying hardware is inherently insecure. It's fast, not safe. Safety is simply not a feature of graphics operations.



You can already do that with fragment shaders. I've already caused my computer to crash and reboot by going a bit to crazy with the fragment shader.


Yep. Browsers could protect against this much better by profiling the fragment shaders instructions, size of data buffers, and requiring the render loop to have a delay. But then we get into managed GL territory and it's no longer really GLES, it's a library that gives you some features of GLES.


Which has been the whole "portability" story of OpenGL, it is similar only in name and some common operations, and that is about it.

In big applications it is like coding to multiple 3D APIs anyway.


I can already imagine the tech support scams




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: