I'm in the same boat. I use Kotlin almost exclusively for my side projects, both JVM and JS stuff, but my work projects are mainly still Java. Some projects are slowly adding a bit of Kotlin, but its just hard to start integrating new Kotlin while most of the app is plain Java. It's just so natural, when fixing a bug in Java code, to just keep writing new Java for it.
I think it's just a matter of time. Kotlin has really only been a "very mainstream" language for a year or so now. As more greenfield projects get started with it, it will get more acceptable to migrate existing projects to it as well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm in the same boat. I use Kotlin almost exclusively for my side projects, both JVM and JS stuff, but my work projects are mainly still Java. Some projects are slowly adding a bit of Kotlin, but its just hard to start integrating new Kotlin while most of the app is plain Java. It's just so natural, when fixing a bug in Java code, to just keep writing new Java for it.
I think it's just a matter of time. Kotlin has really only been a "very mainstream" language for a year or so now. As more greenfield projects get started with it, it will get more acceptable to migrate existing projects to it as well.