11–20 of 31 posts
"36 cities so far. Every visit lights up your dot." You paid to patent this, whatever it is. How about more than two sentences to see what you're charging people for. I can't tell from the website's "About" page. Edit: Even the github link is a 404, I give up.
Plus a 1.8 MB Javascript file ;) ...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.
Plus a 1.8 MB Javascript file ;) ...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.
Plus a 1.8 MB Javascript file ;) ...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.
The 2.7KB WASM is the server-side scoring engine — Zig-compiled, runs on every request at the Cloudflare edge. The globe visualizes where those executions happen.
Two separate layers: WASM at the edge, JS in the browser.
WASM + Zig (even compiling C code) will make some really tiny WASM files with no dependencies. The problem is that you don't have a standard library, then your code gets really big as you add more of that in there.
"36 cities so far. Every visit lights up your dot." You paid to patent this, whatever it is. How about more than two sentences to see what you're charging people for. I can't tell from the website's "About" page. Edit: Even the github link is a 404, I give up.