> especially not when there are other much better and more modern tools. (which Java is demonstrably playing catch-up with)
Which modern tools do you have in mind here?
Java does indeed playing catch up with new features. That's inevitable for a language came out 30 years ago. OTOTH many other languages are still behind Java in terms of the runtime environment and the ecosystem. You should pick what works for you, not to go with the trend.
> The best talent don't even want to consider working with Java if they can help it.
I think you seriously overestimate how talent those devs are if language is the deciding factor of what they choose to work on.
We're talking about Kotlin here (there are many contexts where neither Kotlin nor Java is the correct tool, but for pretty much any use case where Java is an option, Kotlin is going to be a better one)
> not to go with the trend
I'm so sick of this argument, it presupposes that Java is the default and anything else by definition is just a trend. Kotlin is not a trend, Kotlin is not a fad. Stop begging the question.
> I think you seriously overestimate how talent those devs are if language is the deciding factor of what they choose to work on.
Ok, and I think you seriously overestimate the willingness of people who have given Kotlin a serious try and seen first hand how much it offers over Java to go back to working for a Java-heavy shop if they can help it.
Which modern tools do you have in mind here?
Java does indeed playing catch up with new features. That's inevitable for a language came out 30 years ago. OTOTH many other languages are still behind Java in terms of the runtime environment and the ecosystem. You should pick what works for you, not to go with the trend.
> The best talent don't even want to consider working with Java if they can help it.
I think you seriously overestimate how talent those devs are if language is the deciding factor of what they choose to work on.