Context matters. I think kotlin definitely works for android developers but other cases need more thinking. If you're building webapps in smallish teams then m

Context matters. I think kotlin definitely works for android developers but other cases need more thinking. If you're building webapps in smallish teams then maybe those work too. Some reasons against Kotlin are- * If you are working in a mid to large team then having all developers learn a new language is a massive cost. Learning Java is also still a requirement if you're developing in Kotlin since many open source libraries are in Java. So teams need to be aware of 2 similar but different tech stacks. * If you are developing platform libraries then you would look at higher adoption by using Java 11 LTS as the baseline. You could add an optional kotlin library for a better experience. * Others have pointed out how Kotlin will be an evolutionary dead end as Java catches up on features.