I agree with the limitations you mentioned about .Net, but who knows maybe they will switch to a more optimized AOT compilation at some point.
I know TeaVM, but my bet is more on Google side for Java support, the task is too huge for a single person OSS project.
Hopefully JetBrains will be more vocal about Kotlin/Wasm later this year and next year, when it will be more usable with GC support shipped in Chrome stable.
Quite surprised to see no mention of Kotlin here since both languages are very similar, main difference is Swift is LLVM based while Kotlin run on the JVM and has excellent Java interoperability.
I agree with the limitations you mentioned about .Net, but who knows maybe they will switch to a more optimized AOT compilation at some point.
I know TeaVM, but my bet is more on Google side for Java support, the task is too huge for a single person OSS project.
Hopefully JetBrains will be more vocal about Kotlin/Wasm later this year and next year, when it will be more usable with GC support shipped in Chrome stable.