Linked by Jordan Spencer Cunningham on Thu 23rd Jul 2009 19:08 UTC
Google Google announced their O3D plugin for Windows, Mac, and Linux platforms a few months ago, and that was all very well and exciting; this will enable advanced 3D effects to be performed directly in the browser. These new 3D standards on the web will be a very exciting new step in technology. Lately, though, Google has also announced that O3D will eventually be integrated into Chrome. In the words of Greg Spencer, a programmer from Google, "The O3D team is working on getting O3D integrated into the Chromium build, and we're close to being able to complete our first step towards integration. I'll be making the Windows build of Chromium be dependent upon building O3D as part of the build process."
Thread beginning with comment 375067
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: O3D vs. CSS 3D
by raynevandunem on Fri 24th Jul 2009 15:17 UTC in reply to "RE[2]: O3D vs. CSS 3D"
Member since:

Yes, but various parties are pushing their own de-facto implementations of < video >, the outcome of which will be facilitated by the actions of web developers in the deployment of video presentations in their preferred default codecs and which will be decided by the users' direction of attention (and revenue) to their preferred sites through their preferred browsers. The same goes with the browsers' implementations of 3D vector graphics.

Both competitions are involving similar natures of conflict: openness (and FOSS friendliness), extensibility, money allocation towards implementation, intellectual property, scalability, attractiveness, principles compatibility, etc.

Reply Parent Score: 2