Those familiar with the vast world of Android programming and its countless applications in our daily lives will find Java familiar: the primary programming language upon which most programs for our mobile devices, tablets, smartwatches, and more are built. Many believe that while it's not the only way to create such applications, it is the most widespread and accepted. However, JetBrains (the developers of IDEs like AppCode and IntelliJ IDEA) is making waves with its newest statically typed language, which aims to replace the giant Java. Its name is Kotlin, and we're going to explore some of the differences and key improvements it offers.

What's new with Kotlin?

One of the most frequent complaints from the Android developer community is the complexity of performing certain actions/functions in Java. Even with the substantial improvements in Java 8, developers may not be able to benefit from these improvements in the short term.
However, the Czech company is taking another step forward in how we express the internal code of our applications, allowing us to say more with less. In other words, it lets us include less code without affecting application functionality. Another advantage of this language is its syntax, which is quite similar to Java, so it won't be a problem for those looking to embrace innovation. Furthermore, it's fully compatible with Java code, giving us the option to modify existing or completed projects by replacing a portion of the code without having to migrate the entire project. And if that weren't enough, it offers the benefits of a functional language with imperative programming features, as well as unparalleled support for Android Studio, since the developers behind the program are the same people who created Kotlin: JetBrains.

A replacement or a support?

Everything read and discussed by experts on the subject suggests that Kotlin would become a support for Java. However, after the release of its new version last December, more and more professionals are embracing this new programming system, both for its more concise code writing and for its readability and debugging capabilities. We also have to consider other factors that could boost the adoption of this language, such as the increased resource requirements for installing any application, since the Kotlin library itself must be included, requiring longer execution times and resulting in larger file sizes.

That said, does it really represent progress?

Currently, we can say YES. Due to the number of programmers starting to explore Kotlin integration, open-source communities are full of manuals and feedback, making it possible to resolve any doubts on the fly. Furthermore, after its last convention (Google I/O 2017), Google announced that the language would be official for the brand, making it clear that it would have official support.

Our conclusion is that Kotlin aims to eventually replace the current language, but like any change, it will require a transition period. Fortunately, the learning curve is very quick, so we shouldn't be afraid of change.

At SOLTEL we have a small laboratory where we test all the innovative technologies that may have an impact on the market, so that we can have a completely up-to-date technology stack in line with the evolution of the languages ​​themselves.

Sources: code.tutsplus.com, microsoft.com, androiddeveloper.galileo.edu