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.
Well built in garbage collection is non-existent. You can definitely use languages with GCs, you just need to include the GC in the bundle. You can do DOM access as well, it's just not particularly efficient. Overall I think WebAssembly definitely has some usecases, they're just not as visible as people expected. Sites like Figma or Lichess use WASM but not in a super flashy way.
Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
71–80 of 106 posts
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#72Earlier quoted context omitted.
In general I agree with your points, but: > What WASM will never be good at is being used for the whole experience. The Flutter team would disagree. They are leaning on WASM for browser builds of Flutter apps, with the whole app rendering in a canvas. They do accessibility via separately created accessibility trees. The experience far from great at the moment, but give it a few years and I think it will get there. (b…
Unfortunately, Flutter apps still seem to be lagging on the accessibility front. The Flutter web gallery[0] has many examples of beautiful apps, but something as "simple" (on the web) as being able to select text is absent. For some use-cases, this is a nonstarter. (Sadly, not to as many as I'd like! But let's simply not regress , to start.) [0] https://gallery.flutter.dev/
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#73What 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.
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#74What 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.
Good question, still a "green" technology but I have had great successes with it for the past 4-5 years in production (ASM.JS before widespread WASM compatibility). "promising that we'll be able to build web apps in any language" is not how I see WASM, nor is it really used in this way outside of transpiling Unity3D/Unreal games (this may be the one area there is an exception). I use it to transpile C++ to WASM libra…
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#75Earlier quoted context omitted.
There's no garbage collection in WASM. Why do you think that there is garbage collection in WASM? And WASM has been around since 2017, which is only 4 years, not 10 years... Bitcoin has been around much longer (~12 years), for example.
It's a spec proposal. https://github.com/WebAssembly/gc/blob/master/proposals/gc/O...
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#76Earlier quoted context omitted.
There's no garbage collection in WASM. Why do you think that there is garbage collection in WASM? And WASM has been around since 2017, which is only 4 years, not 10 years... Bitcoin has been around much longer (~12 years), for example.
Emscripten hit 1.0.1 around November 2012 (looked it up on GitHub) So if wasm is the spiritual successor to Emscripten's "Compile C to JavaScript and run C in a browser" then it's only 8 years.
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#77Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#78What 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.
Browsers are already pretty complex machines, considering javascript and the DOM and everything that comes along. Expecting all browser to let WASM have access to the DOM is a big demand.
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#79For those wondering, Wasm3 describes itself as "the fastest WebAssembly interpreter". Other webassembly runtimes are JIT based, rather than being interpreters. The project's readme ( https://github.com/wasm3/wasm3 ) talks more about this decision. For more on the difference, and an explanation of what JIT is, check out this section of the book Crafting Interpreters ( https://craftinginterpreters.com/a-map-of-the-terr…
> Other webassembly runtimes are JIT based, rather than being interpreters. Do none of the notable ones do normal compilation?
https://kripken.github.io/blog/wasm/2020/07/27/wasmboxc.html
Re: Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
#80What 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.
Is anyone using a language other than C, C++ or Rust to target Wasm? Many other languages seem to have experimental support - but are any of them ready for production, or even making significant progress towards being ready?