Why Wapka runs on Lua — the architectural decision behind it
Every platform makes a bet on its technology stack. Wapka’s bet was Lua. Here’s why it wasn’t just a good choice — it was the only choice that made the entire platform economically possible. The problem: multi-tenant code execution Wapka lets users write server-side scripts. That means arbitrary code from thousands of users runs on shared infrastructure. In most languages — Node.js, Python, PHP — running untrusted user code safely at scale requires containerization. Docker. MicroVMs. gVisor. These add memory overhead, startup latency, and cost. ...
