We started to experiment with a dedicated Kotlin t...

# webassembly

[Svyatoslav Kuzmich [JB]]

We started to experiment with a dedicated Kotlin to WebAssembly compiler backend. It supposed to generate code directly without LLVM. We are looking to target upcoming versions of Wasm with garbage collector and other post-MVP features.

[sdeleuze]

Awesome, please keep us informed!

[darkmoon_uk]

Faith in [JB] confirmed! Lead us into the type-safe future of browser as another client development 🌅. This could be huge! 🎉

[Tristan Caron]

I supposed thanks to this effort we will be able to have full support for coroutines in the browser?

[bashor]

@Tristan Caron there is Kotlin/JS with the full support for coroutines everywhere where you can run JS 😉

[darkmoon_uk]

Yeah, but JS...

[Tristan Caron]

@bashor I thought it wasn’t supporting multithreading, sorry 😅

[bashor]

you can write in Kotlin, why it’s problem where it’s ran?

[bashor]

@Tristan Caron JS dosn’t support multithreading, but coroutines about asynchronicity than about multithreading. BTW browsers and node.js have a concpt of workers, it’s kind of threads message passing instead of sharing memory.

[Tristan Caron]

JS doesn’t support multithreading, yes. But WebAssembly does. I though targeting WASM and using Coroutine would lead to the possibility to use multithreading, easily.

[sksk]

this is awesome news!

[Sergey Rubanov]

@Tristan Caron in browsers wasm reuses SharedArrayBuffer logic from JS engines. So wasm will get multithreading support as soon as JS will get SAB (enabled in Chrome, in progress in Firefox)

[Tristan Caron]

@Sergey Rubanov thanks for the details