Was going to post in <#C09222272|random> because I...
# k2-adopters
c
Was going to post in #random because I just wanted to start a small discussion, but decided to just put it here. Wondering if anyone might be able to provide insight into why this project from Chris Banes "only" benefited 9% moving to k2. Like some folks in the comments, I was definitely expecting a larger jump (although 9% by just bumping a version number is nothing to sneeze at either 😅) https://twitter.com/chrisbanes/status/1785996503070150745
f
Well if you take in consideration that the goal of k2 isn't to be faster but to make all the existing code compilable with a more maintainable compiler, that's very good improvements
h
the goal of k2 isn't to be faster
Sorry, but that's just wrong. "Optimized for speed" is literally the first thing mentioned in the "key priorities" on the roadmap: https://kotlinlang.org/docs/roadmap.html#key-priorities – sure, it's not the only reason for the rewrite, but it definitely is one of the topmost goals.
t
Kotlin compilation is only a part of project build pipeline, especially for Android projects where a lot of other tools are running (aapt, dexing, etc) so speed improvements could be less than 50% for overall build time
👍 1