It's 2019. Your new Android open source library being written in Kotlin isn't a feature. It's an expectation.
-
Writing it in Java though means you don't get any headaches regarding compatibility in general (sans Nullable/NonNull)
Kotlin extensions are definitely welcome, and using Kotlin for a lib is totally okay, but I don't think it's *necessary*. CMV?
Necessary - no. But unless the library has a specific need to be in Java, I don't see why you wouldn't pick a language that's safer, more concise and guarantees a nicer API for the users. A language that the community has been told for over 2 years now is the future of Android.
-
-
... that doesn't change the fact that there are codebases that are still Java only for Android. If the official Android team hasn't dropped java completely, then it makes no sense to make an assumption either. Having a library on top that provides Kotlin Ext is a better solution.
-
which is why KTX exists side by side of its java counterpart.
Koniec rozmowy
Nowa rozmowa -
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.