Earlier quoted context omitted.
This news sounds quite opposite to me. Although adding a new language is always a good news but Kotlin won't solve any problems with Oracle, since it is just another JVM language. This news sounds like Google is going for an easier way instead of ditching Oracle stuff.
> since it is just another JVM language Not for long, they're working on Kotlin Native which will make it completely independent from the JVM and portable to all platforms. Killer.
Android now supports Kotlin
121–130 of 225 posts
Re: Android now supports Kotlin
#122I hope this will change Jetbrain's attitude towards supporting Kotlin Android rules in Bazel (or anything other than gradle). Last time I asked, they are not very interested[1]. [1] https://discuss.kotlinlang.org/t/android-support-in-kotlinc-...
Don't forget you can use Kotlin to write your build files for Gradle (since Gradle 3.0 was released almost a year ago) which Android Studio auto-completes 100% of the time (rather than 80% of the time as with Apache Groovy). Gradle 3.0 also switched to Kotlin as its "preferred" language for writing addins, so conceivably you could use the Kotlin language for everything in the Android build chain.
Re: Android now supports Kotlin
#123Would be lovely if they officially supported Clojure too.
I am not too familiar with Clojure, what would it bring us that kotlin (or java) don't have ?
Re: Android now supports Kotlin
#124This is pretty big. I really like Kotlin, but when I tried to integrate it into my app, it just didn't play well with popular libraries which rely on compile time code generation (Google's Dagger fork, Icepick, Parcels, etc). Has support for this improved / is it easy to integrate?
Annotation processing works fine with kotlin.
First setup can be a pain though, especially if you are not familiar with Android or the gradle build system.
Re: Android now supports Kotlin
#125Earlier quoted context omitted.
> since it is just another JVM language Not for long, they're working on Kotlin Native which will make it completely independent from the JVM and portable to all platforms. Killer.
That has no value for Google. If Google wanted to get rid of JVM technology and idioms on Android then it would be better off with pure native language like Swift/Rust/Go. They all are quite further away from Javaism. Kotlin's great value is mostly because it is Java like and run on JVM.
This means you could quickly transform any existing app into a Kotlin Native app quickly.
Re: Android now supports Kotlin
#126Oracle winds up killing another golden goose they aquired from Sun. That's what they do though. They buy innovative technology companies who have committed customer bases and then slowly squeeze all the money out of them until they can migrate off. By then they've aquired another set of victim customers.
Not sure what you're rambling about. Java is still and always will be the core language of the JVM. It isn't going anywhere and the Java team (comprising mostly ex-Sun people) continues to push the language forward under Oracle's fantastic stewardship. The issue is that Java is required to be more stable than other languages since it powers so many production, enterprise system and hence will be slower to innovate. I…
Re: Android now supports Kotlin
#127Re: Android now supports Kotlin
#128Anyone know of good online tutorials for Kotlin? I learned Swift for iOS development and customers have been asking for an Android version of my app. Sounds like Kotlin would be a good second language to learn.
Re: Android now supports Kotlin
#129Earlier quoted context omitted.
Why haven't they supported Go on android?
Java, Python and C++ are the actual workhorse languages at Google. Go doesn't seem to be used that much other than a few known projects like the stuff that got re-written for YouTube or the download server. You see this when new Web APIs are released, usually Go isn't part of the preview SDKs, and on Android all the work done on Go mobile has been done by people on the Go team or from the community at large.
Re: Android now supports Kotlin
#130I'm curious to know, just from a general understanding - How much of the situation changes when Java 9 releases? Will it lead to some features in Kotlin becoming redundant/unnecessary, some other new features open up in Java 9, grass-is-greener situations, etc?