This is definitely very interesting! Have you given any thought to support compiling with emscripten?
Okay, that might sound ridiculous, given that one could just load three.js directly in the browser. But moving the internal representation of (and operations on) the scene graph and objects from JavaScript to WASM could potentially give significant performance boosts, especially for real-time/interactive applications running in browsers on mobile/low-end devices.
Okay, that might sound ridiculous, given that one could just load three.js directly in the browser. But moving the internal representation of (and operations on) the scene graph and objects from JavaScript to WASM could potentially give significant performance boosts, especially for real-time/interactive applications running in browsers on mobile/low-end devices.