> Startup time is nil This is obviously not true when the application itself can take arbitrary amount of time to initialize. The overhead of WASM startup is

> Startup time is nil This is obviously not true when the application itself can take arbitrary amount of time to initialize. The overhead of WASM startup is small. But Firecracker is also very quick to start the virtualization; a lean compiled app in Firecracker would start quicker than a bloaty interpreted app in WASM. Both approaches can also freeze a pre-initialized application, and even clone those. Reality is most "serverless" stuff is slow to start because the application itself is slow to start. WASM isn't going to change that, Enterprises are going to Enterprise. The hype field is just very strong.