K2: How to Make a Better Compiler but Keep Kotlin the Same | Simon Ogorodnik

Recording brought to you by American Express. americanexpress.io/kotlin-jobs
As a former TechLead of the K2 project, I’ll tell you how and why we switched from refactoring to rewriting the Compiler Frontend. Beginning the not-inconsiderable journey that brought us to Kotlin 2.0
“We need a better architecture” - probably, everyone in software development heard at least once. However, “OK, let’s make it” rarely follows. But, one does not simply refactor the Kotlin 1.1 compiler to solve its problems. So… We decided to re-write a considerable part of it.
I’ll tell you about:
• Why did we re-implement the huge compiler part, and what does an FIR tree have to do with it
• How we test the compiler and ensure a smooth transition to the new version
• How to make the new compiler but keep the language the same
• Last, what is EAP feedback, and why is it so important

[@starry_shivam]

He seem to be dancing while speaking lol

[@dzartxstudio]

He appears to be so stressed

[@ndrmqaxn]

The cameraman should get an extra cup of coffee XD

[@bennyhuo]

🎉🎉🎉