3 ms·
It's too bad that this kind of thing is using x86 as the actually-pseudocode for this. I understand why -- ease of porting, etc. -- but using either WASM (w/WAL
by api 2y ago
It's too bad that this kind of thing is using x86 as the actually-pseudocode for this. I understand why -- ease of porting, etc. -- but using either WASM (w/WALI?) directly with a kernel compiled to WASM (there are efforts to do this) or something open like RISC-V would be better long term.
- apignotti 2y agoThis is actually running on top of a WebAssembly-based Java Virtual Machine (CheerpJ). You are probably thinking about our independent x86 virtualization product CheerpX (https://cheerpx.io https://cheerpx.io)
- api 2y agoNo, I'm thinking about porting the Linux kernel to WASM itself and not using a VM written in WASM but WASM directly: https://wasmlinux-demo.pages.dev https://wasmlinux-demo.pages.dev In other words, using WASM as if it were the CPU architecture in the VM.