4 ms·

I also would have liked that but developers never jumped on that train. Most apps reside on Android/iOS so the appeal for the consumer and developer is that the

I also would have liked that but developers never jumped on that train. Most apps reside on Android/iOS so the appeal for the consumer and developer is that they also work on a Windows phone Android Java performs really well nowadays. It will be messy to make everything so cross-compatible but I appreciate being able to use my Windows apps on a phone that also integrates with my Android apps. Also, it might save me having to upgrade my desktop. My mobile device might be all I need from now on

pjmlp 5y ago
Android Java performs really well when one is happy to deal with Java 8 subset and cherry picked features up to Java 11, while Java 17 is getting ready to be released, Java is getting a JNI replacement, explicit SIMD, value types, GPGPU support, all stuff that will never show up on Android Java, Google's own J++ flavour. I am looking forward to see if "Google for Games Developer Summit" will finally bring any improvement to the now 10 year long NDK usage pain of writing JNI boilerplate by hand, and C APIs to what is actually written as C++ underneath.
- collaborative 5y ago
  Agreed. I am one of those who is happy to deal with Java 7/8. Newer versions of Java also come with their own set of problems. But the very old Java 7/8 runs really fast on Android and also on Android emulators
- whoisthemachine 5y ago
  Kotlin on Android isn't too bad, but it wouldn't be as necessary if Android's Java compatibility had kept pace with the times. My guess is that they halted that train once the lawsuit from Oracle really picked up steam.
  - pjmlp 5y ago
    Except the little detail that Kotlin and Android Studio wouldn't exist without Java ecosystem, and JetBrains proved their skill in doing the full stack implementation when they borked the design of Kotlin/Native with an incomptible memory model.

4 ms·

I also would have liked that but developers never jumped on that train. Most apps reside on Android/iOS so the appeal for the consumer and developer is that the

by collaborative 5y ago

pjmlp 5y ago
Android Java performs really well when one is happy to deal with Java 8 subset and cherry picked features up to Java 11, while Java 17 is getting ready to be released, Java is getting a JNI replacement, explicit SIMD, value types, GPGPU support, all stuff that will never show up on Android Java, Google's own J++ flavour. I am looking forward to see if "Google for Games Developer Summit" will finally bring any improvement to the now 10 year long NDK usage pain of writing JNI boilerplate by hand, and C APIs to what is actually written as C++ underneath.
- collaborative 5y ago
  Agreed. I am one of those who is happy to deal with Java 7/8. Newer versions of Java also come with their own set of problems. But the very old Java 7/8 runs really fast on Android and also on Android emulators
- whoisthemachine 5y ago
  Kotlin on Android isn't too bad, but it wouldn't be as necessary if Android's Java compatibility had kept pace with the times. My guess is that they halted that train once the lawsuit from Oracle really picked up steam.
  - pjmlp 5y ago
    Except the little detail that Kotlin and Android Studio wouldn't exist without Java ecosystem, and JetBrains proved their skill in doing the full stack implementation when they borked the design of Kotlin/Native with an incomptible memory model.