Java vs. Kotlin

[Killstreak702]

So considering Kotlin by JetBrains has been out for a long while and most Java developers know about it by now, is there any reason why you Java developers haven't made the switch?

It supports JVM (obviously), requires a lot less coding, has null safety, has a lot of cool things like lazy (delegated properties), and a lot more features that makes Java look stupid compared to it.

For you Java devs who haven't seen Kotlin code ever, here's an example:

This is a final variable representing a java.sql.Connection object. "Lazy" is called when the variable is read for the first time. Thread safety is automatic. Normally in Java you'd have a variable like this assigned to null, then initialize it afterwards.

I'd love to see why people prefer Java over Kotlin, I love both (and use Java still for some projects) but after over a month of using Kotlin I haven't found a reason to switch back to Java with what Kotlin has to offer at the same runtime speed of Java.

 

[Blood]

people are too lazy to learn another language even if it means making things more simple in the long run

 

[Killstreak702]

people are too lazy to learn another language even if it means making things more simple in the long run

Seems like that on here for most developers, although it only took me a few days in total to understand Kotlin. I've been using it for like just over a month now. Haven't had a reason to switch back to Java yet.

 

[Astronaut]

Just never really got into it, I wrote a plugin with it as the server I was working for required it, but didn’t really enjoy using it.

 

[Emperio]

I'm a Java dev, and I haven't seen Kotlin going places, as opposed to other languages such as JS(especially with node), I just don't see how I can use it to my advantage. Maybe I'm wrong, but I've been too pre-occupied with perfecting my node.js. And I'm lazy

 

[tuzlu]

For me, it's mostly that there is more documentation on Java. On top of that, I have worked on a server before that had a faulty plugin written in Kotlin and it was a pain to figure out where the actual error came from. Maybe it was my inexperience with Kotlin, maybe it was just Kotlin being weird, I can't say for sure. Java always seemed much more straight forward with the errors.
Kotlin is probably really good once you really get into it but like others have already said it's not worth taking the time to learn.