A few words of possible wisdom to the fine crew at JetBrains: with 1.0.0-rc3 now out of the wild, it seems that you are heading for compatibility with Kotlin 1.5.31 for its release, when 1.6.0 is the current version. While trying to onboard more people to the joy of Jetpack Compose, I find it confusing and irritating to have to tell to rely on an older version of Kotlin. I would bet that most people using Compose for Desktop/Web are staying bleeding edge as they do not have legacy application to maintain. This is at least the case on my multiplatform projects and I wish the lag with Compose would be reduced, even if this means more bugs. I would even suggest to delay the 1.0 version until it works with Kotlin 1.6. Otherwise, I would recommend to communicate better about your release plans, even if they are tentative (and obviously not binding). Just my 2ct 😉

We all want the latest and greatest, just give them a moment ❤️

I would like to add a cent to this guy's 2 cents, so now this post has 3 cents

Umm, I'd prefer fewer bugs over a somewhat meaningless "boast" of working with the latest language version.

Problem is that critical issue with Kotlin 1.6.0 was identified, so we need to wait for 1.6.10 to do migration.

Can we know what the critical issue is with Kotlin 1.6.0?

Might be this https://kotlinlang.slack.com/archives/C3PQML5NU/p1637671562223400

Thanks @Mitchell Syer for shedding light on this 🙂

Hmm. I wondered this too, but mainly from curiosity. I'm loving Compose Desktop!!