It would be nice to know how much WebAssembly actually optimized here vs just writing WebGL in JavaScript. There are too many changes here to know if the speed ups and size gains are related to wasm or just to dumping three.js, and switching all the previous canvas 2D rendering to webgl rendering.
In fact (maybe I missed it), if they're using AssemblyScript is it possible to just run it through TypeScript and check?
Someone else in this post asked the same question and I answered briefly there. Indeed the engine rewrite itself from general purpose to specific usage probably made the biggest difference performance-wise.
However, I do use matrix4 calculations for the 360 viewer, for which Wasm definitely is better.
Interesting idea to do a followup benchmark using the AssemblyScript as TS! I might actually have to do that :D
- If someone posts something in your forum. Can you legally repost in twitter saying.. so and so just posted?
- When you post in a public forum do you automatically assign the copyright as public domain by virtue of where you posted and who can see it?
What is the difference between them posting on your forum and them posting on their on blog/site? Both are visible to the public. If you have some policy written "anything posted here becomes public domain" when maybe but if you don't I suspect it's at best undecided and at worst, "no, it is not okay to repost"
I love the extra hour of daylight in summer evenings and anytime I'm anywhere where it gets darker early in the summer I feel like I'm giving up part of the fun of my life.
It would be nice to know how much WebAssembly actually optimized here vs just writing WebGL in JavaScript. There are too many changes here to know if the speed ups and size gains are related to wasm or just to dumping three.js, and switching all the previous canvas 2D rendering to webgl rendering.
In fact (maybe I missed it), if they're using AssemblyScript is it possible to just run it through TypeScript and check?