Reasons why WASM will not replace containers: - System calls call into the Linux kernel for things like disk and network access. These are highly tested and re

Reasons why WASM will not replace containers: - System calls call into the Linux kernel for things like disk and network access. These are highly tested and reliable. To keep WASMs isolation and portability it would need to replace these APIs with new message passing ones which would kill performance. - C FFI - Dynamic libs Being able to integrate with existing C libraries in the way they are intended to be used. - Better VMs/OS level sandboxing MicroVMs like Firecracker that let you run your code unmodified as if it is running directly on the OS. I like WASM, but feel it is over hyped and the alternatives are “good enough” and already widely used. In the browser it is great though.