Is it possible to get an insight into Kotlin devel...

# getting-started

[Norbi]

Is it possible to get an insight into Kotlin development strategy? I really don't understand some of the decisions regarding the development and advancement of Kotlin.
Just an example: in my opinion Kotlin multiplatform is one of the most important Kotlin feature, and yet it is full of blocker bugs and incomplete core features (eg. Gradle composite build).
In the meantime, the team spends a lot of time developing minor features, like the new range operator. Value classes: it is a great feature and I personally like and use them a lot, but are they really worth the enormous amount of work put into them? The target platforms should and will optimize them in compile/runtime anyway sooner or later.
I don't want to sound offensive, I just really want to understand the priorities, and understand why it is not possible to do a feature freeze until the current functionality has much less bugs...

[Sam]

Not an answer, but some bits of related reading:
• https://kotlinlang.org/docs/roadmap.html
• https://kotlinlang.org/docs/components-stability.html

[Michael de Kaste]

at the last kotlin dev day I attended, I remember that multiplatform kotlin isn that much used (yet) compared to JVM targeted kotlin. Also way more non-android development. You also can't expect an entire team to work on the same epic.

[Norbi]

I see, thanks. I thought that multiplatform is a very important part, and fixing its issues has higher priority than introducing new features.

[BobHy]

Regarding multiplatform specifically, I think Gradle has more blockers than the Kotlin language itself for this scenario, so maybe there's an independent Gradle dev team who's slacking off by comparison with Kotlin language team? After all, I think Gradle has basically solved the problem of JVM builds and that area doesn't need new features (though it certainly will always need bug fixes), so it seems natural they should be able to invest in new scenarios like multiplatform.