After the success of KotlinConf 2017 in San Francisco a follow-up was certainly not outside the realm of imagination. Jetbrains has found a venue that’s slightly better to reach for us Europeans, which is exciting news!
KotlinConf 2018 will be held in Amsterdam from October 3rd to October 5th!
If you are interesting in speaking, the call for papers is open already. More information here: KotlinConf 2018 – Call for speakers.
If you are interested in setting your first steps in Kotlin and live south of the big rivers in The Netherlands, we’ve got good news:
The Eindhoven Java User Group is organizing a Kotlin Meetup on January 30th 2018.
Be there to learn all about the newest JVM language and its feature-set and find some time to interact with other Kotlin enthusiasts.
More info: Kotlin Meetup Eindhoven
Bol.com is planning another meetup covering Kotlin on Wednesday the 17th of February, with speakers from Blue4IT and Bol.com.
The evening will have two main topics, the first talk by Brian Vermeer will be about Java 8, the good the bad and the ugly. Sadly, there’s no abstract to post here, as soon as it turns up we’ll add it to the post.
The second talk by Silvan van Leeuwen and Alan van Dam will cover Kotlin.
As all of us who write Java on a daily basis have experienced, we tend to spend a considerable amount of time writing boilerplate code. We can sometimes refactor that boilerplate away by using specialized classes for certain activities, but that doesn’t always bring us the right results. Reducing repetitive boilerplate can also be achieved by creating a DSL, a domain-specific language that can help us describe anything in a concise and targeted way whilst moving the actual work out of sight.
Kotlin has the tools on board to allow us to write type-safe DSL logic. In this post we’ll dive a bit deeper into how you could use them to your advantage. Here’s a quick preview of what we’ll be building:
This article was originally posted on Medium on December 2017
There’s a saying that “design patterns are workarounds for shortcomings of particular language”. Which would be very interesting, if it wouldn’t come from a Lisp or Scheme advocates around ‘96.
But it seems that Kotlin language designers took this saying really to heart.