3 ms·

Using the same language (Swift) is a great advantage. Java has reached the retirement age, it's time for a better language.

• jmfayard 10y ago
  "for a better language" that interoperate seamlessly with existing java apis and codebases, and had android restrictions in mind during the design phase. Fortunately, this language already exists https://kotlinlang.org/ https://kotlinlang.org/ http://try.kotlinlang.org/ http://try.kotlinlang.org/
  • clumsysmurf 10y ago
    Kotlin doesn't solve any problems for Google from a legal perspective (for example, moving away from the Java ecosystem because of the protracted litigation from Oracle).
    • pjmlp 10y ago
      Google created those problems in first place, by trying not to pay Sun.
    • jmfayard 10y ago
      "Moving away from the jvm" means getting rid of the Android ecosystem. That would be the smartest project management decision since the codebase of Netscape 4 was thrown away
• Zigurd 10y ago
  Most such attempts run up against the particular way that a Java-like runtime is used in Android: The max heap size is tiny compared to desktop, nevermind server Java defaults. You have LOTS of instances of the runtime that depend on the Zygote and copy-on-write so as not to eat all of memory. Component lifecycle has to be handled or you will hate life. Inter-component and inter-process communication and cooperation are deeply rooted in the Android architecture. Lots of the Android OS is built in Java, and takes advantage of Android's runtime limitations and capabilities. In other words, unless you replace Java with another JVM language, you are implying a different OS, not Android with a "better" language.
  • vvanders 10y ago
    Lots of truth here, a new language isn't going to solve things. React Native is probably the closest that you're going to get.