Not sure if only specific to the current project I...

# random

[Pablichjenkov]

Not sure if only specific to the current project I am working on, but updating to Kotlin from 1.8.22 to 2.0.21 decreased the built time in a clean build from ~*6:00* minutes to ~*4:00* minutes.
🙀 wow, this is crazy fast. I still can’t believe it. I am performing some tests to make sure everything is ok but it is really impressive. It is a big project with ~30% still in java, data-binding, view-binding, Fragments, Compose everything you might think of.

[Pablichjenkov]

I was aiming initially to go for Kotlin version 1.9.25 but after seeing this I am jumping directly to 2.0.21.

[Pablichjenkov]

Valid to mention also upgraded Gradle and AGP, this might have helped.

[eygraber]

Out of curiosity, why not 2.2.0?

[Pablichjenkov]

I like small steps 😀. I wait a few months for stability then continue. Also by experience, I prefer being 1 or even 2 releases behind the latest and greatest, just for safety.
Usually preventing issues due to incompatibility of 3rd party libraries not compatible with the latest language version and such. This rule just does not apply to kotlin but any language.

[Michael Paus]

Sometimes the opposite is true too. I just had to switch to the latest Kotlin 2.2.0 in a project, which I actually did not want to update at the moment, because I got runtime exceptions in wasmJs release builds with the predecessors.

[Pablichjenkov]

True, sometimes is the opposite 😅

[galex]

Pls update here what is the improvement with 2.2.0 😄

[Pablichjenkov]

😃😛 Once there I will share 😀. Struggling with targetSDK 35 native libraries 16 KB support these days.