zlacker

Most Java devs are on Java 8, because of how much Java 9 broke reflection, classloading, etc.

>>pie_fl+(OP)
That's something that will likely change pretty rapidly. Springboot 3 is forcing Java 17 which is going to force a lot of conversations once 2 is fully retired. (free support for 2 ends next year)

The Java 8->11 transition was rough but honestly after that we've not really experienced a whole lot of pain. 16 has been a little bit of a pain as well since it closed some more unsafe holes. I think that's the last release, however, that's going to cause major headaches with migrations.

>>cogman+G1
I think Kotlin will see a nice rise in adoption, as the refactoring seems big enough to warrant moving to a language that embraces certain semantics and remove some magic.

I'm speculating though.

>>no_wiz+Ab
Kotlin, IMO, is experiencing the Ruby on rails effect. It's getting strongly associated with android development which has somewhat stifled general uptake of the language.

Java has been slowly adding the best kotlin features (such as data classes, records) which also makes it a bit harder to sell.

That said, I've introduced kotlin on a few teams and pretty much everyone that's worked with it has complimented it.