DEV Community

Cover image for 💘 6 Reasons to Love Kotlin

Posted on • Originally published at on

💘 6 Reasons to Love Kotlin

After a few years of working with Kotlin daily, I reflect upon the six most compelling reasons to use the language.

🔨 The Carpenter’s Hammer

A good craftsman is aware of the tools of his trade and is always critical. If a carpenter bought a new hammer, he would compare it to his old one and reflect on whether it improved his work. I’ll assume the mindset of the carpenter and reflect on my experience of using Kotlin.

What are the “hammers” I’ll compare it with? My personal experience (besides Kotlin) is mostly with Java, Javascript, and Typescript, which I will make my comparisons with. Though I am by no means an expert, working with Kotlin daily for an extended period of time has provided me with enough experience to have an informed opinion. Let’s get started!

💘 6 Aspects I Love

Kotlin is a language with a lot to offer, and most of the time all the attention goes out to the shiny stuff: Data classes, extension functions, operator overloading, you name it. To me, the language’s greatest strengths are more subtle. Let’s see what those are.

🏷️ Names Trump Types

What is the most crucial property of good code? It tells you what it does. Plain and simple.

One of the most effective ways to tell the reader of your code what you’re trying to achieve is with good naming. Thankfully most languages support us well in this regard. When comparing Kotlin to Java, for instance, I like Kotlin better.


Because in Java types come before names. When reading code from left to right (which you happen to do most of the time), the dynamic character length of the type causes the names of variables to start at different points in the code. Take a look at listing 1 for instance:

// Class declaration etc...
public static void main(String[] args) {
    // Important stuff

    String accountNumber = "1234";
    LocalDate birthDate = LocalDate.EPOCH;
    int length = 195;

    // Other important stuff

Enter fullscreen mode Exit fullscreen mode

Listing 1. Types before names are unpleasant to read

Kotlin (and other languages, like Typescript) solve this issue by switching the type and name around, resulting in a better reading experience like listing 2. Kotlin even allows you to omit the type if the compiler can infer it (Java can too, with the var keyword nowadays). This makes the name more prevalent than the type, which makes sense. What are you more interested in? The type of a variable, or its meaning in a specific context?

fun main() {
    // Important stuff

    val accountNumber: String = "1234"
    val birthDate: LocalDate = LocalDate.EPOCH
    val length: Int = 195

    // Other important stuff

Enter fullscreen mode Exit fullscreen mode

Listing 2. Names before types explain more, faster

🗣️ Expressive and Readable

This emphasis on readability continues throughout the language, which I appreciate. Kotlin offers a huge toolbox for you as a developer to choose from, and you can use it to create expressive code.

The offerings of Kotlin are so vast, that I cannot possibly name all of them here. Some of the standout features that I can hardly do without anymore are:

  • Expression functions
  • Extension functions
  • Infix functions
  • Operator overloading
  • When expressions
  • Data classes
  • etc.

Take the humble idea of the expression function for instance. I could write something like this:

fun add(x: Int, y: Int): Int {
    return x + y

Enter fullscreen mode Exit fullscreen mode

Listing 3. Plain old function

Or I could define that same functionality as an expression function (Listing 4). This cuts down on the syntax, as we can omit the curly braces and even the return type since the compiler can infer it. The result is more concise and expressive!

fun add(x: Int, y: Int) = x + y

Enter fullscreen mode Exit fullscreen mode

Listing 4. Expression function: concise and expressive

⛔ Deliberate (Im)mutability

Ever had a bug due to some piece of code changing state on some object, causing issues in another piece of code? That’s all due to mutability. To prevent these horrible bugs, most of our code would ideally be immutable.

Kotlin’s approach to mutability and immutability is excellent. What makes it different? You have to choose: the red pill or the blue pill.

In contrast to Java, making a variable immutable does not mean you have to add a keyword (final). It’s one or the other. Want something to be mutable? Use the var keyword. Otherwise (and preferably) pick val.

Besides variables, Kotlin extends this idea to collections too, which makes it stand out from Java, Javascript, and Typescript. In Kotlin you choose whether you want a read-only projection or a mutable collection. The read-only projections offer methods that will not change the collection. Any operation (filter, map, etc) will return a new collection, as shown below.

fun immutableCollections() {
    val mutable = mutableListOf(1, 2, 3, 4)
    mutable.add(5) // Ok, can add an element to list

    val immutable = listOf(1, 2, 3, 4)
    immutable.add(5) // Doesn't compile, add is unavailable // Ok, returns copy with new element

Enter fullscreen mode Exit fullscreen mode

Listing 5. (Im)mutability is a choice you have to make deliberately

🕳️ Explicit Nullability

Null, “the million-dollar mistake”, the programmer’s dread, and cause of so many bugs. You probably have your own horror stories where you saw the feared NullPointerException (NPE).

Once you encounter this familiar enemy, you’ll have to investigate how it happened. It turns out, that most of the time this will happen because someone wasn’t honest with you. An uncaught NPE usually means that client code did not expect null to be a possible value.


Because it’s not explicit in the signature of a method or property. If it was, you knew you had to deal with it. This is where Kotlin excels. Unless you specify that something is optional (for example String?), the compiler will not allow you to return null.

private fun nullability() {
    var nullable: String?
    nullable = null // Ok, is nullable

    var notNullable: String
    notNullable = null // Doesn't compile, specified as non-nullable

Enter fullscreen mode Exit fullscreen mode

Listing 6. You have to tell the compiler if something is nullable

The compiler forcing you to be explicit about null in the signatures of your code also has effects on consumer code. When they do use code that might return null, they have to take action. Java’s Optional works similarly, but in my opinion, is noisier to read and write. Even worse you can return null instead of an Optional! Effectively this approach relies on programmer discipline, instead of the compiler, making it unreliable.

private fun usingNullable() {
    val nullable: String? = null
    nullable.uppercase() // Doesn't compile, can be null

    nullable?.uppercase() // Safely use nullable reference

Enter fullscreen mode Exit fullscreen mode

Listing 7. You have to take action if something is null

🧰 Swiss-army Knife

The incredibly insightful book Programming Kotlin features a swiss-army knife as its cover. These pocketknives offer a multitude of tools in a very compact form factor which caused the word to become synonymous for something extreme flexible and able to solve pretty much any problem at hand.

Describing Kotlin as one of these pocketknives could not be more apt. I’ve come to love the language for the flexibility it offers in solving problems. I especially love the fact you can employ the language in different ways, suited to the problem at hand.

Need something simple? Use Kotlin to script, no classes required! Want to model complex concepts? Write Object-Oriented code. Is it a more algorithmic or logical problem? Try solving it in a Functional style. Kotlin does not restrict you much, so you can pick and choose whatever you need, all in one convenient package. A true swiss-army knife!

☕ Integrates with Java’s Ecosystem

Java is an incredible language, but it’s more than that. The JVM is an amazing platform. One of the platform’s greatest strengths is the vast community and the solutions it has produced. There are libraries available for virtually every problem.

Kotlin, thankfully, integrates well with this established and mature ecosystem. The interoperability of Kotlin with Java is generally excellent, with some small caveats here and there. This makes it easy to start adopting Kotlin in existing codebases and leveraging both Java code in the project and of third-party libraries.

💔 3 Things I Dislike

Just like any tool, there are some aspects you dislike about it. Thankfully there aren’t many things I dislike about Kotlin, even after extensive use. Let’s have a look.

🛣️ One-Way Interoperability

I mentioned the interoperability with Java as one of the language’s strengths, but there is one caveat. It works well in situations where Kotlin uses Java code. The other way around, though possible, requires more effort.

The Kotlin compiler generates Java bytecode based on your source files. Some of the languages’ features require that bytecode to be… somewhat creative. If you then have to use that code from Java you have to deal with whatever the Kotlin compiler generated, making it less pleasant.

In general, I see the Java interoperability suited best for gradual migration or partial adoption of Kotlin in a codebase.

📦 No Package-private

Kotlin takes a slightly different approach to visibility modifiers than Java and doesn’t offer the package-private option. Now, this might not be a big issue for some projects, but for bigger, more complex projects it can be.

Maintainable code should do one thing and do it well: it should adhere to the Single Responsibility Principle. One way to achieve this is by breaking up complexity, for instance by modularizing code. A package is a way to achieve this, and the package-private modifier allows you to encapsulate details at this level. This way you can refactor implementation details more easily.

The closest thing Kotlin offers is the internal modifier, which hides details at the module level. Module here means a compilation unit, like a Maven or Gradle module. In practice, this forced me to expose more details than I bargained for since everything in a module can access it. It also forced me to create multi-module projects sooner than I liked to.

😳 Accidental Exposure

As you just saw, Kotlin doesn’t offer the package-private access modifier. In Java, this is the default when you don’t specify any of the other options (private, protected, public). Kotlin takes a different approach where the default is public.

Public as the default saves you from writing a keyword here and there, but it takes the explicit thought process of making something public away. Public is the most open and risky modifier. I’ve seen programmers simply forget about the visibility modifiers and code unintentionally becoming publicly accessible.

I would have liked this to be implemented differently. Though the consequences in small projects might not be that bad, in bigger, more complex projects access modifiers are crucial. It allows developers to encapsulate details, making coding easier to change in the future.

📝 Wrapping Up

About three years of daily development with Kotlin has taught me a lot about the language. It would be a challenge to return to other languages that don’t provide the flexibility , expressiveness , and utility that Kotlin does.

I have come to love this language because it helps me be productive. The downsides I have experienced, are therefore easily forgiven.

In the end though, always remember that a programming language is a tool for a developer, just like the hammer is to the carpenter. The tool is just there for him to perform his craft. We’re no different. No one tool is perfect, but for me, Kotlin comes pretty close.

What are your experiences with Kotlin? Did you experience any other pros or cons? Let us know!

Top comments (0)