WebGL Standard To Bring 3D Acceleration To Browsers? 239
Several sources are reporting that while native audio/video support has been dropped from the HTML 5 spec, the Khronos Group has released a few details about their up and coming WebGL 3D acceleration standard. "The general principle behind WebGL is to offer a JavaScript binding to the group's OpenGL ES 2.0 system, allowing code run within the browser to access the graphics hardware directly in the same way as a standalone application can. As the technology would rely solely on JavaScript to do the heavy lifting, no browser plugin would be required — and it would be compatible with any browser which supports the scripting language alongside the HTML 5 'Canvas' element."
Re:i for one ... (Score:3, Informative)
Re:Could someone explain... (Score:1, Informative)
The khronos group is a working group behind the opengl standard iirc
The Khronos Group (Score:3, Informative)
http://www.khronos.org/ [khronos.org]
Re:Could someone explain... (Score:5, Informative)
several sources...are mistaken... (Score:5, Informative)
Re:i for one ... (Score:3, Informative)
Re:Could someone explain... (Score:3, Informative)
Simple answer, yes, the editors should do that. But, in this case, no such thing has happened. The Khronos group is an organisation that slashdotters almost all know as well as the ISO or IEEE.
Re:several sources...are mistaken... (Score:3, Informative)
I think that aforementioned several sources are confusing dropping Vorbis/Theora as a required codec with dropping audio/video elements from HTML5 altogether. Ironically, if you actually open TFA (don't worry, no need to read it) and click on the link that's formed by the words "dropped from the HTML5 spec", the article which opens is indeed about dropping Vorbis/Theora, and it's on the same website. Looks like they don't read their own articles - just like /.
Video/audio did NOT get dropped (Score:4, Informative)
Their just isn't a recommendation about what codecs should be supported in the spec.