You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently things are moving along in the Kotlin/WASM backend, including support for WasmGC in the latest Chrome browsers. This means that a shipped Kotlin/WASM image doesn't need to bring its own GC along for the ride.
Doesn't sound like it's anywhere near ready for prime time, but this is likely to be a much better way to deploy to a browser environment than the Kotlin/JS backend. If it actually works, and integrates properly with HACL.
Apparently things are moving along in the Kotlin/WASM backend, including support for WasmGC in the latest Chrome browsers. This means that a shipped Kotlin/WASM image doesn't need to bring its own GC along for the ride.
Doesn't sound like it's anywhere near ready for prime time, but this is likely to be a much better way to deploy to a browser environment than the Kotlin/JS backend. If it actually works, and integrates properly with HACL.
https://seb.deleuze.fr/introducing-kotlin-wasm/
The text was updated successfully, but these errors were encountered: