Live data from Hacker News

Three.js editor

mrdoob.github.com

71–76 of 76 posts

Re: Three.js editor

#71
post #16

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!

That's right, I was really annoyed that there wasn't a series of explicit compilation steps during development, and that I had access to stuff like live coding.

Re: Three.js editor

#72
post #54
post #16

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!

I can't wait for the day when three.js gets obsoleted. That would mean that someone would have done a free and open source 3d library that is easier to use and with a better designed API. Until then, we'll keep going.

If I could make one recommendation, it would be that you publish the api of three.js in someway that could be parsed by an external tool that might want to overlay a type system - maybe autogenerated from JS docs? There's probably a tool out there already.

I know projects like GWT or LibGDX would benefit greatly from something like this, and personally while I like coding JS, I prefer my prototypes to be in JS and my final code to be in Java. (I know, heresy).

You are doing amazing work btw.

Re: Three.js editor

#73

Earlier quoted context omitted.

I'm surprised that Firefox Mobile supports WebGL (and pretty quickly too). Neither Chrome nor Safari do.

It's weird more browsers don't, considering WebGL is based on OpenGL ES, and most mobile devices implement ES.

It's likely just a matter of perf. on mobile devices. If the browser's rendering/compositing is itself using too much of the GPU's resources to simultaneously run anything worthwhile in WebGL, it's probably not worth exposing it.

Re: Three.js editor

#74

Earlier quoted context omitted.

It's weird more browsers don't, considering WebGL is based on OpenGL ES, and most mobile devices implement ES.

It's likely just a matter of perf. on mobile devices. If the browser's rendering/compositing is itself using too much of the GPU's resources to simultaneously run anything worthwhile in WebGL, it's probably not worth exposing it.

Well, mobile games use the GPU all the time, I don't see why web apps can't. Browsers could prompt before using it, that's what the BlackBerry PlayBook does.

Re: Three.js editor

#75
post #49
post #20

Earlier quoted context omitted.

I wouldn't invest in JS.

What would you invest in? I'm currently working on a small engine for an indy game using JS for the front and backend and am interested in alternatives that are perhaps more future proof.

Well, I don't know what you really mean by "future proof". JavaScript will probably remain the lowest common denominator, for years to come, so from that perspective, there's no safer bet.

However, for people who want to have an edge, as developers, working in their language of choice is one sure way to get it.

There are many different developments to make that happen, like languages that compile to JavaScript, or binaries that run in the browser via NaCL; I think there's a lot of potential there.

... JavaScript was not a language designed with software engineering in mind; that much should be clear. If you can choose the proper language for the task at hand, instead of simply being forced into JS, you'll be ahead.

Re: Three.js editor

#76
post #54

Earlier quoted context omitted.

I can't wait for the day when three.js gets obsoleted. That would mean that someone would have done a free and open source 3d library that is easier to use and with a better designed API. Until then, we'll keep going.

lol

why a downvote?
Post reply on HN