Hacker News Reader

Comment by vbezhenar | Hacker News Reader

Yes, Kotlin is preferred language now. Some new Google libraries are targeting Kotlin first. You should not use Java for new projects.

View on HN

Kotlin is great, but if you're looking for max maintainability in the next ~10 years Java is better. It's just so much easier to hire for Java!

Kotlin is Java++, you can easily hire Java developers and have them working on the code base within days.

I would say Kotlin is Java+ and Scala is Java++

I'm not a 100% sure since I only did basic Scala intro, but it seems like it has a non-trivial learning curve coming from Java - for ex. I was a C# dev with FP experience and it stil took me a while to figure out the basics in Scala. With Kotlin, I barely knew Java and I just used autoconvert and google to simplify my Java code when I was writing some android native stuff.

As an Android dev, I disregarded any company hiring that was not transitioning to Kotlin. It was a major red flag if the project was relatively new. My personal project on spring boot is completely powered by Kotlin and I fully expect KotlinJS to be ready for production in a year or so for full stack development.

Writing in Kotlin really is a nicer experience and with near full access to all the legacy java libraries I would never want to switch back even with the small improvements java has made to be more like Kotlin. I highly suspect as the number of java devs that are exposed to Kotlin increases the number of devs happy to write in Java over Kotlin (or Scala) will decrease. Android going Kotlin first was in part justified by giving the decision makers a short period of a week or two to get adjusted away from java and see how they felt about the language in comparison

I agree with everything you say, but that transition will take time. I think Kotlin is a great language, and combines a lot of the best strengths of others while not giving up that JVM tooling goodness. However, I think you still need to have good Java chops to work with Kotlin, at least to deal with those dependencies. In fact, its almost exactly the situation that TypeScript has: yes, its a good language, but you can't really use it well unless you know JavaScript (and in particular, ES6) really well. Edit: sorry, I'm really talking more generally than Android. You're probably right about hiring for Kotlin for Android instead of Java. But Kotlin is targeted at everything, and for that I think it's probably good to wait a bit.

This sucks so hard. Most Java libraries are planning to drop support for Java 8 when Java 17 hits LTS. This will completely divide the language into two, one for Android and the other for everything else.

Google could just run OpenJDK on phones and toss all the garbage they built, but they're too proud. The GC and performance of ART isn't anywhere near OpenJDK

So you're forced to learn a new language? I was obliged to write code for a university project in Kotlin instead of Java.

Most of the code was already written in Java. So I just used the tool to convert to Kotlin. Then I tried to infer how Kotlin works based on the generated code to write the rest. I don't feel proud about that project.

> You should not use Java for new projects.

Good to know for my next Udemy course.

Reply on news.ycombinator.com