4 ms·
The shithole Google has dug itself and its developers is pretty deep, yet they keep digging instead of partnering with either MS (for C#) or Oracle (for real Ja
by _pmf_ 10y ago
The shithole Google has dug itself and its developers is pretty deep, yet they keep digging instead of partnering with either MS (for C#) or Oracle (for real Java) to get a sane modern language.
But we'll end up with one of the following suboptimal solutions:
- half-assedly backported Java 8 features (with buggy bytecode transformers for libraries that are included in binary form)
- either Dart, Go or (why not go full retard) JS
- pjmlp 10y agoWhen you see their Google IO presentations or interviews, they re-iterate that Java is the only true way on Android, with the NDK just for games and implementation of Java native methods. Then the usual answer to standard Java support is "What features matter to you? Get in touch with us". Is it so hard to see that who usually asks that question cares about 100% of the language or at very least the compatibility profiles?
- 5ersi 10y agoAndroid N supports Java 8: https://developer.android.com/preview/j8-jack.html https://developer.android.com/preview/j8-jack.html
- pjmlp 10y agoThat is not 100% accurate. Android N has partial support for Java 8, it doesn't support all the new Java 8 APIs nor new bytecodes. Additionally, given that Android M is around 10% after one year, how long do you think Android developers can fully target Android N?