I work in digital fields, and I also happen to share my last name with a programming language.
This occasionally leads to confusion. Mostly mild.
Kotlin — the language — was created in 2010.
I was created in 1999.
So technically, Kotlin did not exist before me — but statistically speaking, it will probably outlive me.
There is no deeper story. Just an overlap that makes the domain kotlin.de feel unintentionally fitting.
Because of the recurring mix-ups, I decided to write down what Kotlin — the language — actually is, what it does, and why it became popular.
This is not a tutorial. It is an observation.
What Kotlin Is
Kotlin is a modern programming language created by JetBrains.
It runs on the JVM.
It compiles to JavaScript.
It can be used for Android, backend systems, and, for ambitious people, even multiplatform projects.
It is marketed as concise, safe, interoperable with Java and pleasant to use.
All of these statements are true — to a degree that is almost suspicious for a programming language.
Why Kotlin Exists
Before Kotlin, developers wrote large amounts of Java.
Some still do.
Kotlin was introduced to reduce the amount of code needed to express basic ideas, to avoid common null-pointer issues, and to provide a syntax that doesn’t feel like filling out tax documents.
Kotlin offers:
- type safety without ceremony
- null safety without suffering
- syntax without noise
- and interop with Java without pain
In other words: it solves the problems developers complained about for a decade.
Why Developers Actually Use Kotlin
Developers rarely switch languages for philosophical reasons.
They switch when it saves time, reduces bugs, or prevents them from writing the same boilerplate for the thousandth time.
Kotlin delivers on that.
It offers extension functions, data classes, coroutines and other features that remove the repetitive parts of coding.
It does not promise magic.
It simply removes unnecessary friction.
That alone explains most adoption curves.
Kotlin on Android
Google announced first-class Kotlin support for Android in 2017.
After that, the adoption wasn’t a trend — it was a migration.
Kotlin became the default way of writing Android apps because:
- it reduces code size
- it avoids errors
- it feels modern
- and developers do not enjoy writing verbose Java on mobile platforms
The ecosystem followed. Tutorials, libraries, and frameworks adapted quickly.
Today, Kotlin is the de facto language for new Android development.
Kotlin Multiplatform
Kotlin Multiplatform is an ambitious idea: share business logic across platforms, while keeping native UIs.
It works when used realistically.
It fails when used as a universal hammer.
This is standard for any technology that claims to “simplify everything.”
Still, it is one of the more thoughtful approaches to cross-platform development.
What Kotlin Is Not
Kotlin is not a “Java killer.”
Java is extremely alive, especially in enterprise environments that move at geological speed.
Kotlin does not remove the JVM.
It lives on it.
Kotlin is not a revolution.
It is a refinement — which is exactly why developers appreciate it.
Conclusion
Kotlin — the language — is a pragmatic tool.
Not overhyped, not underpowered, not reinventing anything that didn’t need reinvention.
It simply improves the developer experience in a way that feels reasonable.
For a programming language, that is enough.
That’s the article.
For now.
Leave a Reply