Hey everyone! Asking here since I could not find t...
# k2-adopters
n
Hey everyone! Asking here since I could not find this answer anywhere else. Is there a plan to kill K1 already in plan? Or a clear moment of when it will no longer be supported? Context is me trying to sell why moving to K2 is important. I'm trying to add a "it's unavoidable" argument
👀 1
d
Language version 2.0 is the borderline between K1 and K2 • 1.9 and less -> K1 • 2.0 and above -> K2 So K1 will be still here for some time, but only for old language version. IIRC our current compatibility guarantees, 2.3 will be the last release which will support language level 1.9
👍 1
n
> 2.3 will be the last release which will support language level 1.9 Yeah, that's what I had here as well, but I don't know/remember where I had gotten it from, that's why I was asking here. I wanted to fact check 😅
image.png,image.png
Thanks a ton @Dmitry Romanov [JB], from your phrase here I was able to refine my search and got to this here https://kotlinlang.org/docs/kotlin-evolution.html#compatibility-tools:~:text=we%20support%20the%20development%20for%20three%20previous%20language%20and%20API%20versions%20in%20addition%20to%20the%20latest%20stable%20one. Which to me read like K1 will be supported until 2.2 (inclusive) and will no longer be available on 2.3. Let me know if I'm reading this wrong
d
Yep, you are correct The 2.2 will be the last supporting LV = 1.9
👍 1
e
I "sell" it as a potential faster build times, some better code handling, compose compiler is bundled with and some 2.0 language coming
n
compose compiler is bundled
This one is not related to K2 though
e
What about K2 artifacts compatibility with K1? For JVM there might be no issues, but for the other platforms I'm not sure. This might be another reason to move to K2 (well, be forced to move).
j
If you are thinking about creating your own tooling with custom compiler plugins K2 is a must.