Jilles, thanks a lot for your comment. You point up very important things that I didn't think of. The infamous fight between Google and Oracle was a huge pain for Android devs.
Kotlin is most definitely a first choice language for Android development at the moment when you are starting a new project. Although when you have a legacy app with a big codebase it might be tricky to start using a new language. Despite the interoperability, introducing Kotlin to the existing project may break some tools supporting development. For example, tools that count code coverage, linters, etc may require additional work to adjust everything properly.
Legacy projects that still matter should make an effort to reduce technical debt. Addressing tool issues is a part of that. Kotlin has pretty awesome tooling so addressing issues related to that should not be that hard.
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.
Jilles, thanks a lot for your comment. You point up very important things that I didn't think of. The infamous fight between Google and Oracle was a huge pain for Android devs.
Kotlin is most definitely a first choice language for Android development at the moment when you are starting a new project. Although when you have a legacy app with a big codebase it might be tricky to start using a new language. Despite the interoperability, introducing Kotlin to the existing project may break some tools supporting development. For example, tools that count code coverage, linters, etc may require additional work to adjust everything properly.
Legacy projects that still matter should make an effort to reduce technical debt. Addressing tool issues is a part of that. Kotlin has pretty awesome tooling so addressing issues related to that should not be that hard.