# Java after Kotlin

DevFeed: [Java after Kotlin](<https://devfeed.tech/articles/java-after-kotlin-38656.md>)

Original publisher: [Read original article](<https://krossovochkin.com/posts/2025_02_17_java_after_kotlin/>)

Published: 2025-02-17T00:00:00Z

Content type: opinion

Language: en

Sources: [Vasya Drobushkov](<https://devfeed.tech/sources/vasya-drobushkov.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Java](<https://devfeed.tech/topics/java.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Coroutines](<https://devfeed.tech/topics/coroutines.md>)

Tags: [compare](<https://devfeed.tech/tags/compare.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [java](<https://devfeed.tech/tags/java.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>)

## AI overview

The author compares Java with Kotlin after returning to Java for a coding task. They prefer Kotlin for its conciseness and developer experience, highlighting differences in semicolons, equality, naming, data access, and type declaration, while noting some Kotlin collection and array behavior differences.

## Source excerpt

I am usually pretty slow with new technologies and software updates. That happened with Kotlin a while ago. While version 1.0 was released in early 2016, and many companies were early adopters since the alpha versions, I really started using it only around the end of 2017. I should say that I do find it a very concise and easy-to-write-and-read language. Its focus on developer experience makes it very pleasant to use (except coroutines, lol).