3 ms·
WASM is not strictly for the web, its a generic low-level language target/series of specs. The article itself is talking about server runtimes/workloads, nothi
by adam_arthur 3y ago
WASM is not strictly for the web, its a generic low-level language target/series of specs.
The article itself is talking about server runtimes/workloads, nothing to do with browsers.
If generic specs can be built around WASM in such a way that you can run code securely without booting an entire OS, WASM will replace traditional containers. Smaller runtime footprint.
A consequence of having a generic compile target/spec is that your applications will also be able to run in the browser with minimal effort
- jjtheblunt 3y ago> WASM is not strictly for the web, its a generic low-level language target/series of specs. What about it is preferable to MLIR or even LLVM? https://mlir.llvm.org/ https://mlir.llvm.org/
- adam_arthur 3y agoWASM is designed with security in mind, and specifically to provide primitives for use in a secure runtime. LLVM doesn't provide that to my knowledge... instead just cross-compiling code specific to each target. Correct me if mistaken. I imagine there are meaningful build time drawbacks to compiling an executable for each environment as well. While WASM will never outperform native code, it can get very close. Minor loss in performance is a small price to pay for portability/security.