WebGL Standard To Bring 3D Acceleration To Browsers?

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."

Comments

Fast enough for web browsing??!

[formfeed]

There goes the "fast enough for a little browsing and office apps"-computer. Yes, yes, I know, hardware acceleration will render the pages faster - but more and more sites will include 3d junk.

Praise be to Moore and his irrefutable law:

We are doomed to use faster and faster Computers and more and more energy, to read pages that might - content wise- just as well run on gopher.

Re:Javascript and direct hardware access.

[ivoras]

It's "direct hardware access" in the same sense as the 2D accelerated DrawRectangle() is "direct hardware access".

Re:For the love of god replace javascript

[Hurricane78]

While JavaScript is not perfect, it is actually a nice little language. It's just that every retard can "program" in it, and then thinks because he wrote a for loop, he is entitled to an opinion about it.

Few people actually know how to program properly in JS. And the only problem is that JS is too forgiving. Just as the rendering engines for (X)HTML and CSS. But that was the original point. And it's not that bad of a point either.

Because simple scripts are way easier than people think. Every person who can play a shooter, puzzle game, or configure some stuff on his computer, can write acceptable scripts. And even total noobs can write bad ones. I think that is a nice thing.

And this is why you can ignore the (non-pro) masses, ranting about JS.

If it were for me, the scripting interface in browsers would have to support multiple high-level languages anyway: Python, Haskell, Java and Ruby would be those that I'd introduce. But others might want Erlang, Ocaml, and maybe even C++. Why not? If the API is clean, the interpreters work as expected, and everything is sandboxed as it should anyway...