![]() It was also fun to move away from a language that felt old and verbose, and discover what coding styles fit well with Kotlin’s features. It felt more productive, safer, and the tooling, although not anywhere as mature as Java’s, was good enough to make the adoption worth it. I was blown away by the impact Kotlin had on our codebase. Eventually, most of us were giving it a try. When Google announced Kotlin was becoming an official language for Android development in 2017, another team close to us evaluated the language for their server-side development. But the complexity, pain to work alongside a Java codebase, and slow build times made that language unappealing to most of us. There was some interest in Scala by some teams, and we had a few services already written in it. ![]() We were big fans of IntelliJ and tried to take full advantage of the tooling it provided for Java.Īt that time, we were already looking beyond Java. Our team didn’t follow the typical Java playbook: we used Utterlyidle instead of Spring and embraced a Functional Programming approach with Totallylazy. It’s now almost five years since I wrote my first lines of Kotlin, after using Java for over fifteen years. ![]() ![]() In some specific cases, though, avoiding the adoption is entirely justified. ![]() TL DR - What I see in the wild is that Kotlin adoption on the server-side is slow due to a mix of complacency, career self-preservation, and lack of Kotlin visibility. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |