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.
Exactly right. 2.7KB works because it's pure computation — slot counting, no allocator, no stdlib, no WASI. The moment you need I/O it balloons. This use case fits a glove
"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.
...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.
Fair point — globe.gl (Three.js) handles the 3D rendering client-side.
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.
This is a completely baffling website but as far as I can tell, the 2.7 WASM thing is the MCP runtime this is marketing? The globe thing is independent of that, just showing there the MCP calls are running.
The 2.7KB Zig WASM binary is the scoring engine that runs on every request at Cloudflare's edge. The globe visualizes where those requests land. Two layers — compute at the edge, visualization in the browser.
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.
I'm both fascinated and worried about what the internet will look like in five years.
[1] https://www.faf.one/
[2] https://web.archive.org/web/20150506055228/http://www.timecu...
...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.