3 ms·

Java's supported version on Android is a moot point: all new Android development should be made in Kotlin.

• pjmlp 5y ago
  Pity that Kotlin builds on Java ecosystem and uses that as selling point for adoption. Kotlin libraries on the JVM cannot take advantage of JVM ecosystem, and require KMM to be portable across runtimes, or be constrained to the Android Java flavour. It is like having a flavour of Typescript that only works on Edge.
  • hota_mazi 5y ago
    > Kotlin libraries on the JVM cannot take advantage of JVM ecosystem This makes literally no sense since Android apps are built using not just Gradle but actually the entire Maven Central repo that all Java apps use. Without any changes. If what you said was remotely close to accurate, Android would have its own Maven Central repo.
    • pjmlp 5y ago
      Without any changes! Ah the Google's advocate at his best. Lets not show the people that the libraries that happen to work are those that match Android Java capabilities. Please show us how to use a possible Java 14 library from Maven Central on Android, using records or Panama interop.
• unscaled 5y ago
  That's not entirely a moot point. Java-the-language is mostly replaced by Kotlin and Java-the-runtime is wholly replaced by ART, there is also the Java standard library. New standard library features, or third-party libraries from the Java ecosystem that rely on new language features like records will not be usable.