Also I'd be curious to know if Safari is working on it, I can't seem to find any info about that. 🤔 (maybe you can point me in the right direction @jensimmons?)
It explains the performance and interop benefits. And how targetting WasmGC is like targetting a new VM, with existing LLVM-based implementations not currently compatible.
Languages that have working WasmGC implementations: #Kotlin, #Dart, #Java, #OCaml (wasm_of_ocaml) 😍
@khalidabuhakmeh@range_marten I wonder if the #dotnet team will even use #wasmGC? Seems like there's a lot of tradeoffs good and bad to consider in that article. For example, I can't imagine dotnet allowing anything other than ~99% support for existing language features, and the talk of WasmGC as a VM brings up the concern of unsupported features.
It's also enabled by default in #Firefox (120.0b4). #Safari seems to be the only one out of the picture, as usual, but for many apps (intranet, kiosks) it's safe to assume mainstream browser support.
People interested in tracking WebAssembly Garbage Collection 🗑️ support (aka. WasmGC) in WebKit (and thus hopefully eventually in Safari) should track https://bugs.webkit.org/show_bug.cgi?id=247394. The Garbage Collection proposal adds efficient support for high-level managed languages to WebAssembly, via struct and array types that enable language compilers targeting Wasm to integrate with a garbage collector in the host VM.