I think the advantages come from transpiling languages other than JS to WASM (in their examples, Kotlin and Dart). Eg: An integer in Java, will still be in integer in WASM, while when you ask GWT for an integer, it has to do a bunch of magic, as JS doesn't have integers.
On Sunday, 14 May 2023 at 9:50:58 pm UTC+10 [email protected] wrote: > Thanks for the info. A very good explanation in that video. > > But still don't understand why would this solution with WASM GC 2x faster > than the *"pure transpiling"* solution? The latter is completely in JS > and uses the GC from JS as it is. > > Does this means using JS with WASM will be 2x faster than the pure JS??? 🤣 > > Thanks > Lofi > > Craig Mitchell schrieb am Freitag, 12. Mai 2023 um 12:27:43 UTC+2: > >> At Google I/O 2023, they showed that WASM (Web Assembly) is finally >> getting garbage collection (as well as shared memory). >> >> https://developers.googleblog.com/2023/05/bringing-kotlin-to-web.html >> https://youtu.be/RcHER-3gFXI?t=604 >> >> They showed that JetBrains was experimenting with Kotlin compiling to >> WASM. >> >> There wasn't any mention of anyone doing Java compilation to WASM. >> >> I wonder how hard it would be to modify GWT to compile to WASM. >> Possible? Thoughts? >> > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/edaac5a4-7bdd-42d0-a6af-0909da7d0573n%40googlegroups.com.
