It would be neat to see a difference between this and Unity's WebGL output. I'd expect this would get better performance because it's native JavaScript.
Three.js is just for rendering. Goo Engine is a complete game engine with support for rendering, physics, 3d audio, scripting, state machines, timeline... And there's also Goo Create which makes it super easy even for non-coders to build a scene that can be loaded into the engine.
I'm not sure how to compare extensibility in this case, but both are indeed extensible: For Three.js you might want to add a new class, for Goo you might want to add a new type of component for your entities.
[+] [-] matthewbauer|10 years ago|reply
[+] [-] goocoder|10 years ago|reply
[+] [-] rutigs|10 years ago|reply
[+] [-] schteppe|10 years ago|reply
I'm not sure how to compare extensibility in this case, but both are indeed extensible: For Three.js you might want to add a new class, for Goo you might want to add a new type of component for your entities.
[+] [-] hccampos|10 years ago|reply
[+] [-] redahs|10 years ago|reply
Oddly enough, the lag is much worse at the bottom of the page when the 3D animation is off screen.
Firefox is a bit of the opposite. Scrolling is a slightly choppy at the top when the animation is on screen, but perfectly smooth thereafter.