[anad7]

Kotlin was the worst thing that happened to Android, I mean no disrespect but it seems that JetBrains and its team are really trying very hard to shove Kotlin down people's throat, the sad thing is that despite knowing the fact that it doesn't offer any performance improvements over Java, it is being paraded as the next big thing by overtly excited enthusiasts.

As a user of Android and a developer I want something that enhances the user experience of the apps I use and I create, I want the apps to feel and behave as smooth as iOS, the team at Google should focus on that and not on fragmenting the already fragmented community, right now they are solving a problem that doesn't exist.

I wonder if I would ever see 120/240 FPS apps in the future or if I could offload UI work and animations to a different core because you know your 7 cores are sitting idle and you can do nothing about it.

[biafra]

As as developer I am totally happy that it increases my productivity. You know, you don't have to use it? It is not shoved down your throat. It is a supported offer.

[charleslmunger]

For what it's worth Android has used a separate thread for rendering since API 21. When you implement onDraw, it's really recording the commands and then sending them to the render thread for actual execution.

[rallycarre]

It doesn't fragment the community as you can call kotlin code from java and vice versa. Seamlessly.

Kotlin is great in that it brings Java 8 features to Java 6(lambda expressions, functional programming, etc.) and more. It's a boon to productivity and makes programming in the Java ecosystem fun again.

There is a sometimes increase in compiling speed but it's very marginal and the method counts increase with the transpiling but it's not noticable until the app get's on the larger side.