2 ms·
Fun fact: Microsoft's WebGL implementation calls down to Direct3D.
by bitwize 13y ago
Fun fact: Microsoft's WebGL implementation calls down to Direct3D.
- shmerl 13y agoSure, why shouldn't it (from their perspective). MS didn't enable WebGL out of OpenGL enthusiasm. They did as much as was needed to enable the API on the Web. As I wrote, they didn't drop their OpenGL hostility in other areas yet.
- mcpherrinm 13y agoFunner fact: So do Chrome and Firefox, via ANGLE: http://code.google.com/p/angleproject/ http://code.google.com/p/angleproject/
- shmerl 13y agoFirefox on Windows gives a choice which backend to use (OpenGL or Direct3D). See webgl.prefer-native-gl flag
- corysama 13y agoSomeone correct me if I'm mistaken, but I believe the native OpenGL backend is not recommended for security reasons. All of the security efforts have gone into the D3D backend. The native OpenGL option is included for testing trusted code against a simpler, more reliable, probably faster implementation in case the D3D wrapper is messing up for you somehow.
- shmerl 13y agoNot sure about that, I'm not using Windows anyway, and on Linux it's native OpenGL obviously. Why shouldn't they properly work on security for OpenGL backend though?
- corysama 13y agoPriorities. There are a lot of Windows users out there with old drivers. Many of those old drivers have passable D3D support but useless (if any) OpenGL support.
- Impossible 13y agoSo do Mozilla and Google (by default) when running on Windows. Project Angle (https://code.google.com/p/angleproject/ https://code.google.com/p/angleproject/) is a Google library that enables this in both browsers.