Kotlin Blog

We’re holding another Kotlin Night, but this time in London. We’ve brought together members of the community that have been and are currently using Kotlin in production, to come and speak to us about their experiences. As well as share some tips and tricks.

In collaboration with Trifork and GOTO London 2016, we’re holding this free event on the 12th of October 2016 at the CodeNode venue. We’ll have talks, chats and drinks.
Given spaces are limited, we encourage you to sign up sooner rather than later!

For details on talks, please check the event page.

17:30 – 18:00 – Registration and Welcome

18:00 – 18:45 – 10 Things I’m loving about Kotlin. Graham Tackley. Kaleida

18:45 – 19:30 –  Expressive Kotlin. Nat Pryce and Duncan McGregor, Springer Nature

19:30 – 20:00 – Snacks and Drinks

20:00 – 20:45 – Using Sealed Classes to build Concursus API. Dominic Fox, OpenCredo

GOTO Conference and Kotlin Workshop

We’re also offering a discount for GOTO London 2016 which can be used either for the conference or the full day Kotlin Workshop being held.

Many times we’re asked by people working with or planning to work with Kotlin, what our adoption rate is and who’s using Kotlin and what for.

While we do accept pull requests and run into an occasional tweet we would really like to know first-hand from you, whether you’re using Kotlin in production and if so, how, and what issues you have faced. This not only helps us answer the question when someone asks about our adoption, but learn more about our community. With close to 4000 people on our Kotlin Slack alone, it’s hard to keep track of every piece of feedback!

As such, we’re asking you if you could kindly give us two minutes of your time and fill out the following survey. Please note that by providing us your details, you are not automatically giving us consent to use your name, application or company name. We would ask for written confirmation from you before doing so.

Thank you!

At JetBrains we’ve always believed in our Early Access Program for our tools, giving developers a chance to use the latest features or fixes as soon as they’re ready. We’ve followed the same philosophy with Kotlin, knowing of course that with a language, some decisions can haunt you for life.

That is why during the pre-release days of Kotlin, we’d have milestone releases with features and important changes for our early adopters (including ourselves at JetBrains), collect feedback on whether things were working as designed. This release-feedback-adjust cycle has proven invaluable in so many occasions and has definitely helped shape Kotlin 1.0.

But it’s not over with the release. We’re still continuing to develop Kotlin with new language features and we need your continued support. As you know, we have two ‘branches’ of EAP’s, the 1.0.X ones which are more about bug fixes and tooling, and the 1.1 EAP which is about language changes. And it’s with these EAP’s, the ones with language changes, where we could really use your help. While we don’t recommend you using these 1.1 EAP’s in production code, we definitely do need you to give us feedback. In return, we promise to listen to everything you have to say!

Using EAP’s

The easiest way to access EAP’s is via the Tools menu. Open Tools | Kotlin | Configure Kotlin Plugin Updates in the main menu, select Early Access Preview channel 1.0.x or 1.1 and press the Check for updates now button.

To use the new builds from Maven or Gradle: add https://dl.bintray.com/kotlin/kotlin-eap or https://dl.bintray.com/kotlin/kotlin-eap-1.1 as a repository to your project

At the moment the first EAP of Kotlin 1.1 is available (with coroutines, type aliases, bound callable reference, local delegated properties, Java 7/8 support and many more). Also today we just published first EAP build of Kotlin 1.0.4 with lots of bugs fixes in the compiler and IDE, whole bunch of new intentions, inspections and quickfixes, and it’s now fully compatible with Gradle 2.14.1. For more information check out the full Kotlin 1.0.4 changelog

Giving Feedback

Most of the Kotlin team are available on our public (Slack community), and specifically on the #eap channel, where we’re very eager to listen to your feedback and help with any questions or issues you may have. Of course, our issue tracker is always open too

One of our main goals with Kotlin has always been to make it an industrial language that is pragmatic. And it’s by using Kotlin in many types of applications and scenarios that will help us achieve this goal. For this, we continue to need your help!

Thank you and let’s Kotlin!