...that's too big for a JS shim to talk to browser APIs... it looks more like a complete 3D engine - e.g. three.js or similar?
From that pov the 2.7 KB WASM is a bit misleading (or rather meaningless), it could be a single function call into that massive JS blob where all the work happens.
...that's too big for a JS shim to talk to browser APIs... it looks more like a complete 3D engine - e.g. three.js or similar?
From that pov the 2.7 KB WASM is a bit misleading (or rather meaningless), it could be a single function call into that massive JS blob where all the work happens.