4 ms·
I find it funny how they carefully avoid mentioning Kotlin in the article. Especially considering that it is popular and that they created it. I guess they did
by jillesvangurp 6y ago
I find it funny how they carefully avoid mentioning Kotlin in the article. Especially considering that it is popular and that they created it. I guess they did not want to be party-poopers on Java's birthday ;-).
Basically, Spring + Kotlin is a great combination currently. Spring has first class support for Kotlin and it arguably makes a lot of things easier. E.g. async io with Flows instead of Spring Flux is a lot nicer. I've done several projects with that in the last few years. The Spring people have done a lot of good work in recent years of making it work seamlessly with kotlin. E.g. their flux stuff is a bit clunky but interoperates nicely with Kotlin's co-routines and flows, so you mostly don't have to deal with it.
Also on Android, basically most projects are Kotlin at this point.
- pjmlp 6y agoBecause they are aware that UNIX == JVM and Java has the same ownership role as C has on UNIX. Android is going Kotlin because Google needs a way out of the mess they themselves created. It is quite telling that they purposely always compare Kotlin to Java 7 code samples.
- pron 6y agoBut Android isn't Java, and Kotlin's penetration on the Java platform is ~2-4% and no greater than Scala's (or not much greater, and certainly no bigger than Scala's at its peak). It's a great achievement for an "alternative" Java-platform language compared to others -- and because Java (the platform) is so big, this translates to a respectable number people compared to many other languages, especially when you add the Kotlin-on-Android people to the Kotlin-on-Java people -- but let's not get carried away.