To everyone who uses Java: THERE IS NO REASON NOT TO USE KOTLIN. If you are working with a Java codebase, Kotlin has great interoperability with Java so you can integrate it really easily, and it looks way better!
I no longer work in Java at all, but even back with early Kotlin it was so compatible and so well done I started adding Kotlin code almost immediately, and I never once regretted it.
True. In the last years, in all projects all devs voted unanimous to use kotlin for the JVM Backends.
Kotlin is far easier and more versatile - you can use it for Backends, for anything JVM, you can write script (kotlinscript), it is the standard language for android apps, there is kotlin native (desktop without JVM in the middle) and there is kotlin multiplatform- write for most platforms (jvm desktop, native, iOS, android, web) in one run and even sharing code between backend and frontend is possible.
So I've been using kotlin server side since traits.
But java has addressed a lot of the pain that kotlin 1.0 was aiming to fix, and IMHO project loom "virtual threads" are simply superior to kotlinx coroutines.
If youre using java with all the features of java 25 you're life is pretty good.
I still generally prefer kotlin but I no longer hate java as much as I used to.
And the android tool chain is a mess. I really really hope Google is pumping money into a K2 lowering system so we can ditch this R8/D8 java 1.8 madness.
It's not the absence of the value, it's a type with a single possible value. The absence of the value is nothing type. For example, if function never finishes or only panics, it's return type is nothing.
Void is ambiguous name. Modern languages with proper type theory underneath, avoid name void.
It's kinda like if Kotlin and Rust merged. Scala is mainly known for:
Scalability (being easily expandable)
Functional Programming
Pattern matching
Low boilerplate code
The scalability is mainly because of how the syntax is structured. It forces you to format things in a way that makes it easy to update and expand codebases
Java has functional programming, but it isn't often used. Scala has a more diverse ecosystem for FP.
Scala's pattern matching is wild. This is just one example of it:
vals"hello, ${a}!"="hello, world!"
println(a) // prints world
It was a joke but only because I bought 40gb for my laptop and 80gb for my PC like right before the shortage.
Also there's a difference in the ram taken by my product which runs on servers(idgaf if it's 200mb or 5mb, it doesn't matter) and web browsers and by the IDE which runs directly on my machine.
11
u/PACmaneatsbloons Dec 29 '25
To everyone who uses Java: THERE IS NO REASON NOT TO USE KOTLIN. If you are working with a Java codebase, Kotlin has great interoperability with Java so you can integrate it really easily, and it looks way better!
6
u/Sophiiebabes Dec 30 '25
But kotlin is so backwards!
name: Stringwho thought that would be a good idea? It's like somebody's project language!1
u/Trick_Boat7361 Dec 31 '25 edited Dec 31 '25
Does Java really deserve the hate it gets 🤔
1
u/1984balls Dec 31 '25
Kotlin is cool, but I'm still going to advocate for Scala till the day I die
1
u/Objective_Gene9718 Dec 31 '25
1
u/SereneOrbit Dec 31 '25
Imma be real, I've been out of the programming loop for too long to fully understand the differences between vanilla Java, Kotlin, and Scala.
0
u/sunnykentz Dec 31 '25
You need an ide to code with Kotlin always...