> when a new HTTP request arrives, the VM is ready so you don't need to initialize a different process to manage it. I suspected that, pretty smart. I presume

> when a new HTTP request arrives, the VM is ready so you don't need to initialize a different process to manage it. I suspected that, pretty smart. I presume that a WASM module state can be cached in a similar way, essentially imitating a "fork" syscall semantics while keeping the pool of request handlers in a always-ready hot state.