Hacker News Reader

Comment by flohofwoe | Hacker News Reader

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.

View on HN

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.

Reply on news.ycombinator.com