WASM (and WASI) are interesting and I personally know a lot of people excited about it. We've also ran a few wasm runtimes such as wasmer inside Nanos. Having

WASM (and WASI) are interesting and I personally know a lot of people excited about it. We've also ran a few wasm runtimes such as wasmer inside Nanos. Having said that, there are a handful of technical limitations {raw sockets, 32bit, dynamic linking, performance, security, threads, TLS} that exist today that prevent a bunch of applications being deployed there and while most of them can be dealt with technically I think just because of where WASM descends from (the browsers) there are some organizational (read: standardization) issues that will probably prevent a lot of it from being dealt with. It's been a while since I looked at it but to me none of these are hard technical issues - they are just issues that the WASM community will need to decide in which direction they want to go and how married to the browsers do they want to be.