2 ms·
The Dart & Go teams have projects to target Android but AFAIK these are independent projects with no relation with the Android team. Dalvik -> it is already re
by on_and_off 11y ago
The Dart & Go teams have projects to target Android but AFAIK these are independent projects with no relation with the Android team.
Dalvik -> it is already replaced by ART, but it is still a VM (for ART the bytecode is compiled AOT though).
AFAIK, there is no public plan to replace java, neither are there any public commit on AOSP indicating a move in that direction.
Many Android devs are following Kotlin very closely (it is a boon for Android app development) but again there is no known plan from the Android frameworks team to switch to it.
- V-2 11y agoWhich is a pity. With Google's backing (and they already collaborate with JetBrains, as Android Studio is forked IntelliJ Idea) Kotlin could really grow.
- on_and_off 11y agoit is :( . I hope that Google will reconsider. Being stuck with Java 6.5 is more and more of an issue. You can use ThreeTenABP, Retrolambda and some other libs to get past some of the languages limitations but that's far from ideal. Even if Google switches to OpenJdk 8 (or even 9 or 10), if the adoption times stay consistent, we will have to wait 3 years before being able to use their new features in mature apps. I do hope that either the android team is working on a new language (along with a framework revamp) or will reconsider its position on Kotlin and starts adopting it.
- izacus 11y agoWhy do you expect any other language would have a lower adoption time? Kotlin has to pay the same performance penalties RetroLambda and others do until the device runtime itself is updated.
- on_and_off 11y agobecause kotlin can target devices already in the wild (albeit with a perf cost indeed) whereas languages features added by a new jdk will only be useable with terminals sporting a new version of Android. Just like right now most of us can't use try with resources.