The JetBrains team designed this memory model in an attempt to reduce many of the issues that we encounter once we start working with concurrency. This post is a great overview of the memory model enforced by Kotlin/Native when concurrency is involved. The JetBrains team is aware of this situation. The concurrency story with Kotlin/Native is simply not ready for production. If you have worked with concurrency with Kotlin/Native, then you already know where this is going. Allow me to expand on some of the major pain points that we have encountered. There’s simply no way around that at the current time. However, iOS developers will have a second-rate experience with this technology. In fact, I believe it to be the best solution available for many teams. I don’t mean to imply that Kotlin Multiplatform Mobile (KMM)is not a “good” solution for cross-platform mobile development. I’m here to tell you they have every right to be. Meanwhile, the iOS developer community remains skeptical. It seems obvious that the Android developer community would be quick to sing the praises of a new cross-platform technology delivered by JetBrains.
0 kommentar(er)
