Why Wapka's compute costs are near zero
The numbers tell the story. A Node.js process consumes roughly 30 megabytes of memory. A Python process: 20 megabytes. A Lua state inside LuaSandbox: 1 to 5 kilobytes. That three-order-of-magnitude difference is why Wapka can offer server-side scripting for free. The runtime economics When you let thousands of users run server-side code on shared infrastructure, the cost of each execution matters exponentially. At scale, memory and CPU are the dominant factors. ...