JavaScript performance in all major browsers has shown marked improvements over time, paving the way for it to be used for more sophisticated classes of applications. Many graphics applications, including popular games, leverage hardware acceleration, and subsets of OpenGL (such as OpenGL ES1.1) are already available on smartphones. The initial activity proposal is to consider a simple binding of OpenGL ES2.0 to JavaScript, and exposing that to an HTML5 Canvas context. This is how a 2D drawing context is exposed to the web for use with a JavaScript API; the proposed mechanism is to do this for a 3D context as well. As exciting as this is for the web and for us at Mozilla, it’s worth explaining our choices, and raising some questions.

We chose Khronos to start with, since that’s the home of OpenGL, and the proposal is to start with an OpenGL subset such as OpenGL ES2.0. This is a very low-level API with a lot of C language structures, and perhaps an early task for the working group would be to figure out how to expose that to JavaScript. This isn’t a fait accompli, and we look forward to help and collaboration from other major players. Naturally, security is a paramount consideration. Google announced support for the activity, and we look forward to others doing so soon as well.

Would web developers actually use something this low level? While we anticipate the influx of a new type of web developer (who may also be a games developer, or interested in 3D visualization), it’s worth pointing out that a standardization principle that’s served the web well is to expose pretty low level primitives in browsers, and allow third party JavaScript libraries to take on the task of syntactic sugar and higher level abstractions. Applications toolkits such as dojo, jQuery, and Prototype simplify developers lives; the same can occur in the 3D arena.

It’s also worth pointing out that this endeavor with Khronos to bring a subset of OpenGL to the web is just the first step. Higher level APIs with retained mode graphics are likely to follow suit. The discussion officially started yesterday, so we’re glowing with fresh possibility in uncharted terrain here.

Also read Vlad’s thoughts on all this — he wrote the extension that was the initial experimental implementation, and made this happen. And Chris Blizzard’s thoughts.