Kotlin 1.0 Released: Pragmatic Language for JVM and Android

This is it. 1.0 is here!

It’s been a long and exciting road but we’ve finally reached the first big 1.0, and we’re celebrating the release by also presenting you with the new logo:


See discussions on Reddit and Hacker News

What is Kotlin?

Kotlin is a pragmatic programming language for JVM and Android that combines OO and functional features and is focused on interoperability, safety, clarity and tooling support.

Being a general-purpose language, Kotlin works everywhere where Java works: server-side applications, mobile applications (Android), desktop applications. It works with all major tools and services such as

  • IntelliJ IDEA, Android Studio and Eclipse
  • Maven, Gradle and Ant
  • Spring Boot (Kotlin support released today!)
  • GitHub, Slack and even Minecraft :)

One of the key focuses of Kotlin has been interoperability and seamless support for mixed Java+Kotlin projects, making adoption easier leading to less boilerplate code and more type-safety. Additionally, Kotlin has an extensive standard library that makes everyday tasks easy and smooth while keeping the bytecode footprint low. Of course, any Java library can be used in Kotlin, too; and vice versa.

What does pragmatic mean?

Understanding one’s core values is crucial for any long-running project. If I were to choose one word to describe Kotlin’s design, it would be pragmatism. This is why, early on, we said that Kotlin is not so much about invention or research. We ended up inventing quite a few things, but this was never the point of the project. Of course we were building a type system that prevents bugs, and abstraction mechanisms that facilitate code reuse, as anybody in our position would. But our (pragmatic) way of doing it was through focusing on use cases to make the language a good tool.

In particular, this approach lead us immediately to the notion that interoperability with existing code and infrastructure is crucial. Re-writing the world the right way, all from scratch — who never wished to? I did, quite a few times :) And Kotlin would have been a whole lot easier to design and develop if not for the Java interop, Maven integration, Android compatibility! It would definitely be more elegant in many ways. But elegance, though highly appreciated, is not the primary goal here, the primary goal is being useful. And the less our users have to re-learn, re-invent, re-do from scratch, the more they can re-use, the better.

So, why doesn’t Kotlin have its own package manager, or its own build system?
— Because there’s already Maven and Gradle, and re-using their huge number of plugins is crucial for many projects.
Why did we invest a lot of time and effort into making JDK-compatible collection interfaces, when it was so much easier to just redesign collections from scratch?
— Because tons and tons of Java code work with JDK collections, and converting data on the boundary would be a pain.
Why does Kotlin support Java 6 byte code?
— Because many people are still running Java 6 (Android, most notably, but not only Android).

For us pragmatism is about creating user experience, not a language or a library alone. Many of the language design decisions were made under constraints like “Won’t this impede incremental compilation?”, “What if this increases APK method counts?”, “How will the IDE highlight this as-you-type?”, and many more like these. As a result, we are proud of our tooling as well as the language.

Is it mature enough and ready for production?

Yes. And it has been for quite some time. At JetBrains, we’ve not only been implementing the compiler and tooling but have also been using Kotlin in real-life projects on a rather extensive scale over the last two years. In addition to JetBrains, there are quite a few companies that have been using Kotlin in production for some time now.

In fact, one of the reasons it took us a long time to reach 1.0 was because we paid extra attention to validating our design decisions in practice. This was and is necessary, because moving forward the compiler will be backwards compatible and future versions of Kotlin must not break existing code. As such, whatever choices we’ve made we need to stick with them.

Reaching this milestone was something we couldn’t have done without the valuable help of early adopters. We want to thank each any every one of you for your bravery, energy and enthusiasm!

Who’s behind Kotlin?

First and foremost, Kotlin is an Open Source language

  • Developed on GitHub under Apache 2.0 Open-Source license;
  • With over 100 contributors to date.

JetBrains is the main backer of Kotlin at the moment: we have invested a lot of effort into developing it and we are committed to the project for the long run. We wrote it out of our own need to use in our own products. And we’re happy to say that to date, close to 10 JetBrains products, which include IntelliJ IDEA, JetBrains Rider, JetBrains Account & E-Shop, YouTrack as well as some of our smaller IDE’s and some internal projects are using Kotlin. So it’s here to stay!

Since 2012 we kept Kotlin’s development very open: talking to the community all the time, gathering and addressing lots of feedback.

Moving forward we are planning to set up a centralized venue for design proposals and discussions, to make the process even more visible and organized. Standardization efforts have not been started for Kotlin so far, but we realize that we’ll need to do it rather sooner than later.

Language design and overall steering of the project is done by the team employed at JetBrains. We currently have over 20 people working full time on Kotlin, which also yet another testament to JetBrains’ commitment to Kotlin.

The numbers

Let’s take a look at some numbers:

Talking about lines of code, the number of these in open repositories on GitHub is growing exponentially over time (JetBrains’ projects excluded):

Kotlin GitHub Adoption

And of course we have a growing list of companies using Kotlin including Prezi and Expedia. By the way, if you’re using Kotlin, make sure you send us a Pull Request.

The upcoming roadmap

As of 1.0, we are committed to long-term backward compatibility of the language and its standard library (kotlin-stdlib):

  • a newer compiler will work with older binaries (but older compilers may not understand newer binaries, like javac 1.6 can’t read classes compiled by javac 1.8);
  • older binaries will keep working with newer binaries at runtime (newer code may require newer dependencies, though).

This applies to the JVM/Android support only. The JavaScript support remains experimental for now and will have its own release later on.

As for the plans, our nearest goals are (apart from bug fixes):

  • Constant performance improvements for the Kotlin toolchain (this includes, for example, incremental compilation in Gradle, that is in the works now);
  • JavaScript support (including cross-compilation into both JVM and JS where possible);
  • Support generating Java 8 byte code with optimized lambdas, etc (Java 6 will be actively supported as long as Android users need it).

Tooling updates and bug fixes will be released as incremental updates, i.e. 1.0.X. Bigger changes will first go though an Early Access Program (EAP) and then will be released as 1.1.

How to start

The easiest way to play with the language is through its online mini-IDE: try.kotl.in, including Koans — a set of introductory problems which guide you through the basics of the language.

To use Kotlin on your machine (and Koans can be completed offline as well):

  • IntelliJ IDEA (Ultimate or Community): just create a Kotlin project or a Kotlin file in a Java project;
  • Android Studio: install the plugin through Plugin Manager;
  • Eclipse: install the plugin through Marketplace.

NOTE: If you are running an older version, you may need to update your Kotlin plugin to 1.0.

To get up to speed with concepts, language docs and tutorials are available from the official web site. Great articles and presentations given by members of our community can be found in the Digest of 2015.

If you’re introducing Kotlin to your Java project, you can make use of the Java-to-Kotlin converter built into the IDE, helping migration easier class by class.

Last but not least, make sure you join the discussions on our Forum or Slack.

Once again, we want to thank everyone. We couldn’t have done this without the community.

Have a nice Kotlin! Now :)

P.S. See discussions on Reddit and Hacker News

About Andrey Breslav

Andrey is the lead language designer of Kotlin at JetBrains.
This entry was posted in Releases. Bookmark the permalink.

111 Responses to Kotlin 1.0 Released: Pragmatic Language for JVM and Android

  1. Rob Bygrave says:


  2. Sergey Igushkin says:

    Awesome news. Congratulations!

  3. svd says:

    Well I have been following Kotlin from its first baby steps until now.
    I really am quite happy to see 1.0 finally.
    Congrats Andrey and also to the whole team!

  4. Pingback: Developing Spring Boot applications with Kotlin | Alexius DIAKOGIANNIS

  5. M Platvoet says:


  6. Francis Fredrick Valero says:

    Congratulations Andrey and the whole Kotlin team!!!!!!!!!!!!!!!!!!

  7. Pingback: Kotlin 1.0 Released: Pragmatic Language for JVM and Android | Kotlin Blog – Temporary index

  8. mintori says:

    Well done team!

  9. Adambl4 says:

    New era began in the android development.

  10. Salomon BRYS says:


  11. Kittinun Vantasin says:

    Awesome!! Great job JB and the team.

  12. Oliver Plohmann says:

    I read this comment by Andrey some days ago: “We are planning to publish 1.0 very-very soon (think days, not weeks)”. I thought that would be too good to be true. But it was true! Congratulations! We have a real alternative to Java now :-)

  13. cypressious says:

    Congratulations! You make Android dev fun again.

  14. Максим Наумов says:

    А вот я с критикой. Что на счет KT-10691? Это же наследование, одна из самых базовых вещей, без которой языка не было бы. И с багом.
    Кажется, у вас становится нормой выпускать “финальные версии” с багами (это я намекаю на AppCode).

    Нет, я пользуюсь Kotlin начиная с последних бета-версий, и уже настолько подсел на него, что больше не хочу возвращаться к Java. А при любой возможности советую его друзьям и знакомым. И именно поэтому мне хочется, чтобы Kotlin был безупречным. На практике это означает, что я хочу иметь возможность делать с его помощью не меньше, чем с помощью Java. Но вот кое-что не могу.

    Ведь именно безупречная работа продукта приносит удовольствие от работы с ним. И по большей части так оно и есть. Но недостатки вроде указанного выше – ложка дегтя в бочке Kotlin.

    Надеюсь, что вы правильно меня поймете. А еще надеюсь, что вы все же начнете фиксить все до единого известные баги прежде, чем называть что-то релизом.

  15. Eugene says:

    Great news!

  16. This is fantastic! Congrats!

  17. QuangSon says:


  18. Arild says:

    Fantastic (much anticipated) news! Congratulations!

  19. Congratulations! Developing and releasing a new language, and one that has received such warm reception, is no easy task. Kotlin is an interesting language, and I hope to see it in use for many years to come. Congratulations all around for JetBrains and everyone that contributed.

  20. Steve says:


  21. Peter says:

    Congrats and thanks for creating this awesome new langauge! Can’t wait for more people to adopt Kotlin.

  22. Misha says:

    No more breaking changes!

  23. Artem Borisovskiy says:

    Excellent news. Writing in Kotlin is so much fun compared to Java :)

  24. Cliff says:

    Excellent work and my heartfelt congratulations!

  25. Nik says:

    I hope you guys will fix kapt issues in the future.

  26. Yehonatan Levi says:


  27. David Vydra says:

    Congrats! Would love to have a tech talk at GE Digital in San Ramon, CA.

  28. Steve Holmes says:

    Congratulations, Gents! And let me also congratulate you on having a clear vision. I think it’s one of the most compelling reasons to use Kotlin in production.

  29. Julius Kunze says:

    Congratulations, this is amazing!

  30. Oliver Thomas says:

    Nice one, team Kotlin!

  31. Laurent says:

    I wrote a serie of 4 posts about Kotlin. That’s in French but Google Translate usually works well enough. Conclusion: Kotlin has the potential to supplant orchestration scripts like Python, Ansible, and some others.

  32. Mohammad Sarbandi says:

    Awesome. Congratulations!!!

  33. Pingback: Kotlin 1.0 Is Now Available and the Newest JVM Language Is a Breeze -

  34. Craig says:

    I want to use it. Can you point me where to start? Keep in mind I need more experience with JVM stuff in general.

  35. Pingback: Kotlin, the ‘pragmatic’ language for Android and JVM, has reached its 1.0 release | Prague City Magazine / Beat Blog | human views on the ins and outs of prague, czech republic

  36. Pingback: El lenguaje “pragmático” Kotlin ha llegado a su versión 1.0 | Adictec

  37. Johannes says:

    Now we just need Google to use Kotlin as main language for Android…

  38. Skin27 says:

    Congrats. A small line of Kotlin, a giant leap for app development.

  39. Michał Kowol says:

    Good job!

  40. Jens Driller says:

    Congrats on the 1st official release!

    Good job. Keep it up! :)

  41. ken says:

    Great work!

    Hope the backward compatibility is true…have worked w/ some frameworks where everything breaks on the next version and it was a giant pain :-(

  42. Pingback: Reading List 02/15/2015 – thehumble.ninja

  43. Pingback: JetBrains Releases v1.0 Of Kotlin, A Smart JVM-Compatible Language That Can Be Used To Write Android Apps

  44. Pingback: Kotlin 1.0 Released: Pragmatic Language for JVM and Android | thoughts...

  45. kuno says:

    Congratulations, guys.

    Really great jobs has been done!

  46. Reza says:

    Congratulations, this is really great news.

  47. Pingback: Kotlin 1.0 Released: Pragmatic Language for JVM and Android (jetbrains.com) | ..:: Frog in the box ::.. | ..:: Frog in the box ::..

  48. Pingback: Kotlin 1.0 Is Now Available and the Newest JVM Language Is a Breeze | Ranfind Web Programming

  49. Pingback: Kotlin 1.0 Released: A Pragmatic Language for the JVM and Android | Ranfind Web Programming

  50. foobra says:

    Will you guys talking to Google and consider tread Kotlin as the default language in Android deveolopment?

  51. borrom says:


  52. Pingback: Kotlin 1.0 正式版发布 基于 JVM 的编程语言 | 客家网络

  53. Pingback: JetBrains Launches v1.0 Of Kotlin, A Smart JVM-Compatible Language That Can Be Utilized To Compose

  54. Pingback: Elkészült a legújabb Java-gyilkos nyelv, a Kotlin 1.0-s verziója - Hírek - Prog.Hu

  55. Pingback: 안드로이드와 JVM을 위한 개발 언어, ‘코틀린’ 1.0 출시 – 캐스트몬

  56. Pingback: 안드로이드와 JVM을 위한 개발 언어, ‘코틀린’ 1.0 출시 – Soohong Park's Blog

  57. Suresh says:

    Awesome news.. Congratulations!

  58. Pingback: Yested FW updated to Kotlin 1.0.0 | Yested Framework

  59. Анхбаяр says:

    Nice! Congraz :)

  60. Christian says:

    You did a really great job! In many projects Kotlin will be the only alternative to Java. Kotlin is very readable, robust and equipped with good tooling from the start. Thank you, JetBrains!

  61. Congrats! I’m already using Kotlin in my Android projects. So far it’s great!
    I’d also done a presentation about Kotlin during our company’s Lightning talks.
    Take a look here – Kotlin Developer Starter in Android projects.


  62. Pingback: 正式发布Kotlin 1.0:JVM和Android上更好用的语言 | 江清清的技术专栏

  63. Pingback: JVM-Sprache Kotlin in Version 1.0 erschienen - JAXenter

  64. Pingback: JVM-Sprache Kotlin in Version 1.0 erschienen

  65. Pingback: Java-Herausforderer: Programmiersprache Kotlin in Version 1.0 erschienen | t3n

  66. HE Guangyu says:

    Congratulations. Thank the Great Team!

  67. Mikhail says:

    Concerning “and future versions of Kotlin must not break existing code. As such, whatever choices we’ve made we need to stick with them.” – Are you sure if it’s right choice?
    What’s wrong if in 10-15 years (when there will be other programming paradigms) – changing/updating language syntax to support new concepts. Once in 10-15 seems – it seems not huge problem.
    I think you as nobody else know what “perpetual backward compatibility” means in practice like in Java: defective generics implementation, outdated bad collection design etc. It seems in a 5-10 years – you can get the same issues when implementing new syntax concepts.

    We already have Java with perpetual backward compatibility and all related issues with it, why you decided to choose the same way?

  68. Pingback: Vulkan 1.0 specification announced, Kotlin 1.0, and Rackspace unveils Data Connectors—SD Times news digest: Feb. 16, 2016 - SD Times

  69. Pingback: xvoda | JetBrains’ Kotlin JVM language appeals to the Java faithful

  70. Pingback: JetBrains’ Kotlin JVM language appeals to the Java faithful | Datainterpreters

  71. Pingback: JetBrains' Kotlin JVM language appeals to the Java faithful | POPALZ News – Latest news from Pakistan

  72. Pingback: 안드로이드와 JVM을 위한 개발 언어, ‘코틀린’ 1.0 출시 – 캐스트넷블로그

  73. Richard Gerlocke says:

    Gratz again…. This is the first I’ve heard of Kotlin, but I will try it out in Android Studio tonight!

  74. Pingback: JetBrains' Kotlin JVM language appeals to the Java faithful – Online Marketing Gurus Program

  75. Pingback: JetBrains releases Kotlin 1.0, a better coding language for Android apps – Android Community

  76. BASIL says:


  77. Pingback: JetBrains' Kotlin JVM language appeals to the Java faithful | Sub-Planet Java Codes

  78. Pingback: Help Kotlin with syntax highlighting - naijaknow

  79. Sofus Mortensen says:

    Excellent news! Good job, thanks!

  80. Sanu K Soman says:

    Congratzzzz !.. Now its time to start Kotlin programmimg :)

  81. Pingback: Links 17/2/2016: Vulkan 1.0, GNU C Library Vulnerability | Techrights

  82. Pingback: Hello, Kotlin: Another programming language for JVM and JavaScript - GeekTechTalk

  83. snail says:


  84. xzgyb says:

    Congratulations!! I concern kotlin all the time. Now it release 1.0 finally.
    Very thanks!

  85. Tim van der Leeuw says:

    Release of the 1.0.0 version got me curious again so I started playing around a little bit with the REPL, after looking at a couple of examples.

    I found it almost trivially easy however to assign NULL to a value of type String – java interop is the weakness here.

    Has this already been reported? If not, I feel bad for not trying out these things earlier :-(

    Copy pasting from my REPL session in IntelliJ, so errors are not part of the console output:

    var s1: String = “s1”
    Tim van der Leeuw

    s1 = java.lang.System.getProperty(“user.name”)

    s1 = java.lang.System.getProperty(“none”)




    • The fact that this code is allowed is the expected behavior: we can’t help it much when we interact with Java (we tried to be more strict here, and it has proven very impractical). In pure Kotlin you have a lot more type-safety than in Kotlin+Java, but even with this kind of cases we can catch a lot of bugs statically.

      What is a bug here is that this code fails too late: it should have thrown an exception when the actual null was assigned to s1. Please report this issue. Thanks!

  86. Pingback: Interesting Stuff – Volume V | Krzysztof Góralski

  87. Pingback: Kotlin и Vulkan 1.0 — Episode 0080 « DevZen Podcast

  88. Pingback: Engraved on Closed Tabs – Eric Schrag

  89. Pingback: Weekend resources for new Kotlin programmers — Global Nerdy - Joey deVilla's mobile/tech blog

  90. Pingback: Kotlin 1.0, Google Go 1.6 und Blockchain: unser Wochenrückblick - JAXenter

  91. Pingback: Kotlin: ¿un lenguaje de programación más? | unocero

  92. Pingback: Developing Spring Boot Applications With Kotlin -

  93. Pingback: Kotlin 1.0 – Pragmatic Language for JVM and Android Released | Lo Sviluppatore

  94. Duy Bui says:

    Owesome! Congrats team.

  95. Pingback: Kotlin 1.0 – Language for JVM and Android | Fernando Franzini Blog

  96. Pingback: Szumma #027 – 2016 7. hét | d/fuel

  97. Pingback: Tab Closing, Everything Must Go – Eric Schrag

  98. Minimum says:


  99. Pingback: Os 10 links do mês - Fevereiro | Blog da Concrete

  100. Pingback: IntelliJ IDEA 16预览版更新了哪些内容? - IT大道

  101. Pingback: Kotlin(1) - 初探与集成 Android 项目 - IT大道

  102. Pingback: Java Annotated Monthly – March 2016 | 神刀安全网

Comments are closed.