Hey team is there a roadmap for the new Kotlin Wasm compiler

Question

Hey team is there a roadmap for the new Kotlin Wasm compiler backend or is just a case of it will be ready one day

Big Chungus · Answer

It s waiting for wasm gc mainly

kailan · Answer

Ah that makes sense thanks for the speedy reply Is there a way to use the deprecated wasm32 target from Konan outside of a browser context or is it reliant on the arena allocation methods etc from the engine

kailan · Answer

for example if i wanted to run a kotlin app in wasmtime <https github com bytecodealliance wasmtime>

Big Chungus · Answer

No clue I ve only used it in browser scenario

Daniele B · Answer

< kailan> you can follow this issue

kailan · Answer

fantastic thank you

kailan · Answer

My team seem to be under the impression that Wasm GC is years out from being usable is this commonly known

bashor · Answer

< kailan> with new compiler backend we mostly are focused on browser usecases one of reason is that we don t see much interest from standalone VM vendors to new GC proposal We would happy to change it and collaborate with standalone VM vendors too

bashor · Answer

Another point is that at some point somebody can create convertor from `Wasm with GC` to `Wasm without GC` which allow us an other projects simply run even on VMs w o GC proposal support

bashor · Answer

also this could relevant for you <https kotlinlang slack com archives CDFP59223 p1594049904021800>

bashor · Answer

Implementation in Kotlin Native is self contained and use own memory manager produced binary theoretically could be run inside any Wasm MVP VM But NOTE we are going to deprecate and remove it in the foreseeable future

bashor · Answer

In near future we ll update <https youtrack jetbrains com issue KT 42292|the related roadmap issue> stay tuned

ESchouten · Answer

Forgive me for my ignorance my knowledge isn t anywhere near sufficient enough to realize the magnitude of work needed for the following question Couldn t the new Kotlin native memory model be reused in Kotlin Wasm until the official GC is implemented <https blog jetbrains com kotlin 2020 07 kotlin native memory management roadmap > I understand shipping a garbage collector to each users browser is far from ideal size and performance wise but couldn t it boost Kotlin Wasms development

Big Chungus · Answer

The team decided to prioritize other things rather than chasing current LLVM based KWASM that s already deprecated Given the colossus that kotlin multiplatform is seems like a sensible decission if you ask me

Big Chungus · Answer

Also I wouldn t expect new K N memory model until 1 6 at the earliest