I fear that three.js will be more or less obsolete with the rise of emscripten/asm.js which allows basically any 3D Engine there is to Run inside the browser. There is still some work todo in regards to quicker deployment but i wouldnt invest heavily in pure JS based engines right now as there will be tremendous leaps in this space (eg Unreal Engine3) in the coming months. That being said, this is an awesome Tool!
Well , where are these 3d engines ? do i have to code in C++ ?... you get my point...
Three.js editor
31–40 of 76 posts
Re: Three.js editor
#32Re: Three.js editor
#33For those curious, this works great on mobile (Firefox on a Nexus 4)
Re: Three.js editor
#34Re: Three.js editor
#35I fear that three.js will be more or less obsolete with the rise of emscripten/asm.js which allows basically any 3D Engine there is to Run inside the browser. There is still some work todo in regards to quicker deployment but i wouldnt invest heavily in pure JS based engines right now as there will be tremendous leaps in this space (eg Unreal Engine3) in the coming months. That being said, this is an awesome Tool!
I wouldn't invest in JS.
Surely we must know better in 2013.
Re: Three.js editor
#36Wow this is really impressive—just out of curiosity, how did you show the standard Mac OS X color picker from the browser window? That particular bit seemed very cool for some reason :-)
Re: Three.js editor
#37Earlier quoted context omitted.
I wouldn't invest in JS.
This, so much. I can't believe companies are pushing to port everything to one of the worst language in existence. Okay, I get the benefits of easy deployment, but what about performance, debugging, ecosystem, typechecking, compile-time optimizations, general engineering, etc.? Surely we must know better in 2013.
Re: Three.js editor
#38Earlier quoted context omitted.
I wouldn't invest in JS.
This, so much. I can't believe companies are pushing to port everything to one of the worst language in existence. Okay, I get the benefits of easy deployment, but what about performance, debugging, ecosystem, typechecking, compile-time optimizations, general engineering, etc.? Surely we must know better in 2013.
Re: Three.js editor
#39Earlier quoted context omitted.
I wouldn't invest in JS.
This, so much. I can't believe companies are pushing to port everything to one of the worst language in existence. Okay, I get the benefits of easy deployment, but what about performance, debugging, ecosystem, typechecking, compile-time optimizations, general engineering, etc.? Surely we must know better in 2013.
Like it or not these developments are turning JS into a bytecode for the web. Maybe one day there will be other language options but why not invest in making the best of what we do have?
Re: Three.js editor
#40For those curious, this works great on mobile (Firefox on a Nexus 4)