skiko

o render on the web as well, if you compile to WASM target. There's the big Kotlin event going on right now, where they just announced the new WASM backend and changes in their compiler + IR commonizing/restructuring ("K2"). - https://blog.jetbrains.com/kotlin/2021/10/the-road-to-the-k2... - https://www.youtube.com/watch?v=-pqz9sKXatw The net result is that you wind up with a single language that you can use to write your backend API, your UI code (Jetpack Compose app deployed across Web/Android/iOS/Mac/Win/Linux, or transpile to JS/TS if you just want a web app, etc) and with Kotlin Native even your native, low-level code to integrate with existing C/C++ etc ecosystem. KN already does automatic bindgen for C and Swift headers, they have direct C++ interop (like Swift does) on their future roadmap too: (Ctrl+F "interoperability") https://kotlinlang.org/docs/roadmap.html#roadmap-details All of this is mostly possible already -- I can do the same thing using IE Java, GraalVM, and a transpiler like Google's j2cl or bck2brwser (which is what Gluon uses for JavaFX on the web). Including the "native" part. IE, here's a contribution I made to get GraalVM producing native binaries using Skia from the JVM + JNI Jetbrains Skia library (and even invoking my Java app methods as a .dll from C++) https://github.com/HumbleUI/JWM/issues/158 But Kotlin is pushing the hardest to make this whole platform/stack from native <-> desktop <-> mobile <-> browser a seamless, unified experience. And you can feel it, when you try to do the "whole stack, every platform, one language" thing. Sorry for the rant and wall of text!