Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Tried Kotlin, honestly I was not impressed. Tools (maven/gradle) wasn't as straight forward to setup as one would have expected. I am not impressed with the language itself and I had issue with conflicting libraries and kotlin versions.

I switched back to modern Java and did not regret it.

Java is catching up at a fast pace, I don't think Kotlin will ever replace Java or see mass adoption.



Kotlin has already pretty much replaced Java for Android devs. I see it doing something similar to Java use more generally (albeit more slowly than it did with Android).


Of course it did, Google is making that decision a reality.

On the JVM, Kotlin doesn't matter, it is just another language that pretends to be Java when compiled to Java Virtual Machine bytecode.


> Of course it did, Google is making that decision a reality.

It was already hyped up and rapidly gaining popularity for Android devs prior to Google endorsing it. That's why Google endorsed it.

> On the JVM, Kotlin doesn't matter, it is just another language that pretends to be Java when compiled to Java Virtual Machine bytecode.

I mean sure, but this applies to replacing Java elsewhere too.


Scala and XTend were being hyped the same way.

If Google wasn't playing dirty, they would have kept updating Android Java to be in line with Java, and let the developers choose.

Instead, they purposely stagnate Android Java on a Java 8 subset, let the Android marketing machine push Kotlin over Medium articles, Twitter blog posts, YouTube Android developers channel, Android developer blog posts, MAD training material.

And lets not forget the role of JetBrains, having had a role replacing Eclipse with InteliJ in what concerns Android Studio, now they even dropped support for Eclipse on their Kotlin support, as they are quite open that they want to use Kotlin to drive InteliJ license sales.

Kotlin is just another flavour of CoffeeScript in what concerns the JVM.


It's 3 lines in a build.gradle(.kts) to get running. We've been using it in production for 5 years without any issues you are describing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: