I think this is a much worthwhile project...

[mcanthony]

I would be more than willing to help keep this baby alive... I have this fantasy that I could customize/hack a transpiler/build system into semi-automagically generating a Portable Native Client implementation of any given JS code-base... What would you (as someone who has done simular porting by hand) say to such malarkey?

The work you have done in directly (not just in spirit) porting ThreeJS and all of its JS idioms may not have been in vien. I have a feeling this might be of much use to me in enabling the NaCl/PNaCl code to work in harmony with the original JS code-base (this may turn out not to be all that needed though).

I see this "Generator" also spitting out a native-implemented node module for use with server side/offline rendering or perhaps with the likes of atom-shell (or whatever it is now) and Node-Webkit (NW.JS).

I would love to know what insights you may have into this being a worthwhile endeavor, or if such a thing would be all that useful. People seem to pump out a lot of Chrome only "experiments" that fail to leverage Chrome's full capabilities.

Short of the magical compiler ecosystem thingy majiggy I would like to further what you have done here in order to put together a PoC Native Client build of ThreeJS in order to factor the true performance benefits. Chrome/Chromium would seem to be a massively easy platform for cross platform distribution of 3D, especially if one did not have to create a custom build to accomplish this.

And if a user can just land on the site with a Blink based browser and run the app with 99% native code execution.. well, I just dont know what to say.