4 ms·
No, they aren't. The host is equally memory safe with a WASM guest as with any other fully sandboxed embedded system, of which Java is not. And everything you m
by pie_flavor 2y ago
No, they aren't. The host is equally memory safe with a WASM guest as with any other fully sandboxed embedded system, of which Java is not. And everything you mentioned isn't any more memory safe running in the same process as in a foreign process, which was, again, the bar you set.
- tliltocatl 2y agoI think we disagree on what memory safety is. For me, memory safety is about "not being able to type-pun pointers and access stuff out-of-bonds", rather than just "isolate address spaces". > fully sandboxed embedded system, of which Java is not How so? Nothing stops JVM from sandboxing within the same address space. Then the java API breaks sandboxing in many intended and unintended ways, but the advantage of WASM here is that it doesn't provide a standard API at all - every attempt to provide same functionality will run into similar issues.