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.
It's really annoying that you can stop the globe from rotating. This also feels exactly like a Claude-built website, which is unsurprising.
Looks like they just updated it. Check under the globe.
use the pause button below it, zoom in/out, rotate too
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
thanks for visiting — the globe just crossed 100 cities - Appreciate the feedback. Happy Sunday :)
"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.
Thanks for flagging the broken link. More context here: https://mcpaas.live/about
MCPaaS is trademarked. Nothing it patented.
Looking at the website of the organization [1] of the author, linked at the bottom of the submitted link, I get serious Time Cube [2] vibes.
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...
Fair feedback — the homepage was overdue for a cleanup. It now points to the repo: https://github.com/Wolfe-Jam/faf-cli
What do you sell? Names? Names for what? Site is kinda laconic…
[dead]
It there some law that mandates all 3D globe renderings auto rotate and omit any way to stop it?
use the pause button below it
Thanks! I see that just got added.
What in the slop? I have rarely seen so much of it concentrated across just a few domains
Fair — the homepage needed work. Updated to repo: https://github.com/Wolfe-Jam/faf-cli
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.
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.
Ah ok, might have made more sense to link to the about page tbh, but that probably would have looked too obviously like an advertisement ;)
just trying to show the zig-wasm binary and CF edge :)
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.
Three.js alone is ~400KB uncompressed.
Yep — Three.js renders the globe client-side. The 2.7KB scores server-side at the edge. Separate concerns.
[dead]
[dead]