What is the state of the world with wasm at this point? It seems like it's been this huge tease for 10 years now, promising that we'll be able to build web apps in any language. But as far as I'm aware, garbage collection and DOM access is still nonexistent.
For those wondering, Wasm3 describes itself as "the fastest WebAssembly interpreter". Other webassembly runtimes are JIT based, rather than being interpreters. The project's readme (<a href="https://github.com/wasm3/wasm3" rel="nofollow">https://github.com/wasm3/wasm3</a>) talks more about this decision.<p>For more on the difference, and an explanation of what JIT is, check out this section of the book Crafting Interpreters (<a href="https://craftinginterpreters.com/a-map-of-the-territory.html#shortcuts-and-alternate-routes" rel="nofollow">https://craftinginterpreters.com/a-map-of-the-territory.html...</a>)
I'm a newer dev so pardon my ignorance. Is webassembly the new, more open JVM? Feels like that write once, run everywhere but this time with any(most) mainstream language.
Self-hosting (compilers) <a href="https://en.wikipedia.org/wiki/Self-hosting_(compilers)" rel="nofollow">https://en.wikipedia.org/wiki/Self-hosting_(compilers)</a> :<p>> <i>In computer programming, self-hosting is the use of a program as part of the toolchain or operating system that produces new versions of that same program—for example, a compiler that can compile its own source code</i>
Has anyone built a compiler extension and libffi-based runtime that supports compiling otherwise normal native code to WASM (eschewing hard linking for runtime resolution)?<p>Would be fun to make it so that native apps for any platform can be run from an interpreter
I feel the need to repost this link:<p><a href="https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript" rel="nofollow">https://www.destroyallsoftware.com/talks/the-birth-and-death...</a>