> If we were to write new components in Kotlin, we would be making the problem worse. At this point in time Java is our safe fallback. I don't agree with this.

> If we were to write new components in Kotlin, we would be making the problem worse. At this point in time Java is our safe fallback. I don't agree with this. Kotlin is essentially a drop-in replacement for Java, so much so that you can replace your Java classes _one by one_ with Kotlin classes. The build tools, frameworks etc are mostly the same, so no real changes required in the environment. (All this is not true for Scala, for example.) From one perspective, one might argue that Kotlin didn't do enough (eg. it has ADTs but no pattern matching), on the other hand, this is exactly why it is so easy to step up. You can also very quickly get productive in it coming from Java, there is no need to use advanced stuff like async/await, and there are very few caveats you need to worry about. Just my 2c, based on experience.