🙋♂️ INFO: If you have fixes/suggestions to for this doc, please comment below.
🌟 STAR: This doc if you found this document helpful.
I try to push for quite a long time for first class support for WebAssembly in Kotlin because I really believe that frontend development is a domain where Kotlin can be as strong as in mobile, and because this is something that would also help to increase even more the adoption on server-side.
I truly appreciate all the work already done by Kotlin/JS and Kotlin/Native teams. The dead code elimination tool and the initial WebAssembly support in Kotlin/Native are important steps in the right direction. But I believe that Kotlin needs now to make frontend a real priority to take it to the next level.
The first point I would like to raise is that what Kotlin needs IMO is a consistent strategy about web frontend wich includes both Javascript and WebAssembly related efforts. I can u
<!-- slap this somewhere at the top --> | |
<style> | |
/* the lines within the edges */ | |
.edge:active path, | |
.edge:hover path { | |
stroke: fuchsia; | |
stroke-width: 3; | |
stroke-opacity: 1; | |
} | |
/* arrows are typically drawn with a polygon */ |
class A { | |
fun shout() = println("go team A!") | |
} | |
class B { | |
fun shout() = println("go team B!") | |
} | |
interface Shoutable { | |
fun shout() |