Hacker News new | ask | show | jobs
by dakiol 510 days ago
I worked for a startup that used Kotlin. The language itself is not that bad (if you ignore the engineers that want to use every single time all the features the language has to offer), but the ecosystem was awful. We were using Gradle, and Spring Boot: just too much magic for my taste. Gradle itself is a beast I never fully understood, and I don't comfortable working with such tools (the Gradle userguide has over 1000 pages https://docs.gradle.org/current/userguide/userguide.pdf)

On the other hand, Go is a breath of fresh air; the tooling is simple and one can actually learn them in no time. There's less magic, and so a bit more of repetition, but I can live with that.

I don't see the advantage of having the JVM to be honest. I just don't see why it would be needed in 2025 (the "Write once, run anywhere" is not relevant anymore).

2 comments

JVM's advantage has not been "Write once, run anywhere" for a long time - we all run code in docker containers anyhow. The real advantage is stability and tooling availability
Gradle and Spring Boot are not a part of the JDK, so it seems unfair to discount Java due to their poor designs.