March 29, 2026
Spin me right ’round, devs
Show HN: 2.7KB Zig WASM – live globe showing executions at 300 CF edges
Tiny code, big spin: devs roast the nonstop globe and the "2.7KB" flex
TLDR: A tiny 2.7KB Zig WebAssembly demo shows a live globe of Cloudflare edge hits, but users slammed the nonstop spin, vague details, a 404 GitHub link, and a hefty 1.8MB JavaScript file. The debate: clever minimalism or misleading marketing—why the kilobytes flex if the megabytes do the work?
A flashy demo dropped: a live spinning globe showing code running on 300+ Cloudflare edge locations, boasting a teeny-tiny 2.7KB Zig WebAssembly (WASM) file. The crowd? Immediately seasick. “Is there a law that all 3D globes must auto-rotate with no off switch?” one user groaned, while another called it a “Claude-built website,” roasting the vibe as AI-generated. Then came the size-math drama. A sharp-eyed commenter spotted a chunky 1.8MB JavaScript file likely powering the graphics, calling the tiny WASM claim “misleading” if the heavy lifting lives in a massive script. Cue the classic internet split: marketing flex vs reality check. Trust took another hit when someone hunting details found vague copy (“Every visit lights up your dot”), alleged a paid patent, and hit a 404 on the GitHub link—chef’s kiss for vaporware accusations. To be fair, one dev stepped in with nuance: yes, WASM + Zig can be truly tiny when you skip the standard library; add it back, and the size balloons. Meanwhile, the globe ticked through hits from Atlanta to Frankfurt, and some users saw retry messages, fueling the snark. Verdict from the peanut gallery: cool idea, but stop the spin, show the code, and don’t hide the megabytes behind the kilobytes
Key Points
- •A live globe visualizes where a 2.7KB Zig WebAssembly binary runs across Cloudflare’s edge network.
- •The page shows real-time metrics including 10,776 executions and 84/175 active locations.
- •A “Top Locations” list ranks cities by execution count, led by Atlanta (ATL 8,205).
- •The interface indicates “Cloudflare Edge MCPaaS Live” and updates on a “60 Refresh” interval.
- •Status messaging such as “Failed to load globe data. Retrying...” reflects live data retrieval.