> Why would you want to implement "a kernel" in WebAssembly? Because webassembly has all the problems (very old) physical hardware has. No multithreading, but

> Why would you want to implement "a kernel" in WebAssembly? Because webassembly has all the problems (very old) physical hardware has. No multithreading, but a kernel can cheat that out (by rewriting user space programs or interpreting them). Cooperative multithreading is a central component of virtually every webassembly program (ie. we're at win3.1 level). There's uses for drivers, dynamic libraries, permissions, ... all of these concepts have uses it seems to me very similar to what you need on real hardware.