3 ms·
> So, the conclusion: no we don't need a swift for Android, I think we do, and to me, that language is Kotlin: Analysis: http://goo.gl/wNjXoU http://goo.gl/wN
by zak_mc_kracken 11y ago
> So, the conclusion: no we don't need a swift for Android,
I think we do, and to me, that language is Kotlin:
Analysis: http://goo.gl/wNjXoU http://goo.gl/wNjXoU
The language: http://kotlinlang.org http://kotlinlang.org
- on_and_off 11y agoKotlin also looks like the most serious contender to me. Sure, something like Rust might be more interesting for various reasons, but the engineering effort needed to port the Android framework to another language would be huge (and the official word from the Android framework team is that it is not worth the effort). Not to mention that third party developers would have to relearn the framework from scratch and that we either have a windows mobile 6 / WP7 rift or the framework team has another nightmarish problem to solve. Kotlin looks like it could both guarantee retro-compatibility with Dalvik and brings a better language to the platform.
- zserge 11y agoTotally agree with you! Kotlin is great replacement for Java on Android. I like to see that more and more interesting libraries appear for Kotlin, like Anko. I recently made Anvil compatible with Kotlin (http://zserge.com/blog/anvil-kotlin.html http://zserge.com/blog/anvil-kotlin.html), which makes UI development a pleasure