3 ms·
If you are going to target WebAssembly outside of a browser environment, uh, why not just target LLVM, GNU, or uh, you know, Assembly... X86_64 or ARM are prett
by nicetryguy 6y ago
If you are going to target WebAssembly outside of a browser environment, uh, why not just target LLVM, GNU, or uh, you know, Assembly... X86_64 or ARM are pretty standardized. Another part 1/1 "tutorial" with some brilliant insight as per usual.
- Jyaif 6y agoBecause WebAssembly allows you to sandbox the code, which you can't with regular assembly.
- otabdeveloper4 6y agoSure you can. The so-called "virtual machines" have existed for a while now. :)
- geofft 6y agoThere seems to be a section in the article called "Why would we want to run WebAssembly outside of a browser?" that I think addresses what you're asking?
- Skinney 6y agoLLVM bitcode is, I believe, not portable. Neither is Assembly. Nor are the resulting binaries of that processed something that is run within a sandbox.
- aerismio 6y agoThis, i think webassembly is the sweet spot. It has portability but doesn't have any opinion about how the code should be structured. No opinion about GC or objects etc. Works really really great with Rust.
- juntao 6y agoYes. Because WebAssembly provides a higher level of abstraction (safety, isolation, portability, manageability etc — you know, the “enterprise” stuff) over native code. See here: https://www.secondstate.io/articles/why-webassembly-server/ https://www.secondstate.io/articles/why-webassembly-server/