I just want to add some general comment about Kotl...
# kotlin-native
g
I just want to add some general comment about Kotlin JVM and Native interoperability. I understand that K/N not intended to fix JNI problem, but I think it would be a really good starting point for K/N, same way as interop with Java have been a good starting point for Kotlin JVM. For example in our case most of app code is Kotlin/JVM, but we have a big native part on C/C++ because of performance (realtime audio processing) and to share code with iOS and (probably in future) Web. And JNI support is really tedious and unnatural. But! If we would have good interop Kotlin/JVM to Kotlin/Native or direct interop to C using K/N tools (like -flavor=jvm) we would be happy to use it instead of JNI and it will give us a good opportunity to adopt K/N for our native layer and not only for interop, but also as good option to share code for all our platforms and as replacement for C/C++ for some not performant critical parts (for example we have a lot of Json work in native and would happy to use Kotinx.Serialization or just Kotlin for such code). I’m not a native guy, but interop with K/N and C would allow me and my team to be closer to our native developers and combine effort with them.
➕ 6