Seems to be missing the "why" over Kotlins native WASM support (which is very mature)
The official Kotlin playground uses WASM, for example (JVM drop down-> choose "WASM")
Seems to be missing the "why" over Kotlins native WASM support (which is very mature)
The official Kotlin playground uses WASM, for example (JVM drop down-> choose "WASM")
I think that compiles WASM in the server, whereas this compiles in the browser.
I'd challenge the 'by hand' assertion though.
WASM mode still works with no network, so it can't be relying on the server.