This year we want to work a bit more on promoting the Dutch Kotlin User Group (NLKUG). We are looking for bloggers and/or other Kotlin enthusiasts in the Netherlands who want to help us out.
With a big thanks to appdevcon.nl we will be promoting NLKUG @ appdevcon.nl this year. If you want to meet us there you can still buy tickets with a discount voucher specially for NLKUG visitors. The following voucher entitles for a 5% discount for the appdevcon.nl conference: nlkugp20
Four days ago, Kotlin version 1.3 was officially released to the general public. This release adds a lot of highly anticipated features, amongst which are:
Coroutines now stable: After being an experimental feature for quite some time, Jetbrains have now decided the time has come to mark coroutines as a stable feature. It is not integrated in the core language, but still an add-on that Kotliners can opt-in for.
Several minor features added to the language, compiler and/or tools and plug-ins, amongst which:
Experimental support for inline classes (for better performance
Experimental support for unsigned integers
When expressions now expose the subject so you won’t need to assign it to a variable yourself
Kotlin’s built-in null-safety makes it easy for us to write code that’s less error-prone and less susceptible to the unwanted and unexpected NullpointerException at runtime. We can do a lot to make sure it doesn’t happen, but sometimes there’s no way around dealing with possible null-values. Kotlin is introducing Contracts in the upcoming 1.3 release (currently m2) in which we can use contracts to tell the compiler how a function behaves and what results are implied, so we can benefit from improved smart-casts.
Apparently everybody’s favourite JVM language beat Java in a recent code-smell contest. The Register reported on a paper by Bruno Gois Mateus and Matias Martinez who had carried out an extensive survey of the rate of Kotlin usage in recent open-source Android projects. Well, they’d have to be fairly recent, wouldn’t they. Using the Paprika tool to sniff out anti-patterns, they reached the not so surprising conclusion that the Kotlin code under scrutiny smelled a lot better than your average Android project in Java.