Yeah, and i like their choice:
[[
JavaScript performance across browsers can vary greatly. An O3D
application may perform well in one browser while not performing
adequately in another. There are a number of causes for this
difference. Some JavaScript engines interpret JavaScript code, while
others compile it to native code. Some browsers host plug-ins in the
same process as the browser, while others host them in a separate
process, leading to a high overhead for calls between JavaScript and
the O3D API.

To mitigate these issues, the O3D plug-in embeds the V8 JavaScript
engine. This is the same high-performance JavaScript engine found in
the Chrome browser. An O3D application using the embedded JavaScript
engine instead of or in addition to the browser's own JavaScript
engine may see improved performance, more consistent performance
across browsers, and sometimes significantly lower overhead when
calling between JavaScript and the O3D API. A disadvantage of this
approach is it is no longer possible to debug such JavaScript code in
the browser's JavaScript debugger.
]]

2009/4/22 Giuseppe Luigi Punzi Ruiz <glpunzi at lordzealon.com>:
> This looks interesting.
>
> http://code.google.com/intl/es/apis/o3d/
>
> Cheers.
>
>



-- 
Best regards,
Igor Stasenko AKA sig.