3 ms·
Just think of how far we got in recent years: C++ code compiled to asm.js, JITted and running in browser running on OS running in virtual machine running on OS
by dexen 13y ago
Just think of how far we got in recent years: C++ code compiled to asm.js, JITted and running in browser running on OS running in virtual machine running on OS running on a microcoded CPU -- and GLSL shaders compiled to ARB, running on microcoded GPU.
Next thing you know, antivirus software for web browsers (sic) will become the norm.
- TazeTSchnitzel 13y agoWhy would web browsers need anti-virus software? It's not really a problem, since the web's APIs enforce a lot of sandboxing and hence security.
- quux 13y agoWebGL is pretty scary since it's only a thin wrapper around OpenGL. OpenGL drivers tend to run in the kernel, have direct access to the complete memory of the box and not be hardened from a security perspective. It's only a matter of time before someone figures out a way to own a box via WebGL by simply visiting a website. This is why Apple leaves WebGL disabled by default in Safari, and I think Microsoft is hesitant to add support in IE for the same reason.
- gcr 13y agoI agree. There was a recent time - maybe a few months ago - where Linux with nvidia hardware and their binary driver blob would instantly panic the system when I visited a page in firefox that used webGL shaders.
- lern_too_spel 13y agohttp://www.opengl.org/registry/specs/ARB/robustness.txt http://www.opengl.org/registry/specs/ARB/robustness.txt
- TazeTSchnitzel 13y agoWebGL is more secure than OpenGL. It helps a lot that the major browsers don't implement WebGL with OpenGL on Windows. Chrome and Firefox implement it with DirectX.