Please register yourself on our Meetup page

Hello Kotlin enthusiasts!

We are excited to invite you to our Kotlin meetup on January 18th. This is a perfect way to kick off the new year and learn from other passionate developers. Come join us, and let’s make 2023 a year of growth and development. We can’t wait to see you there!

Location:
Wibautstraat 200 – 202, Amsterdam

Timeline:
18:00 Doors open, food and drinks
18:30 Kotlin & Project Loom: Blessing or doom? –Urs Peter
19:30 Kotlin Multiplatform + Domain models = ❤️ –Nico Krijnen
20:30 Chats & Drinks

Kotlin & Project Loom: Blessing or doom?
Urs Peter

Finally: Project Loom has been officially announced for Java 19 as a preview feature! Loom will be a game-changer for the JVM’s concurrency model, delivering ‘reactive’ characteristics out of the box without the need for complex concurrency abstractions.

Regarding Kotlin, the concurrency features project Loom offers are already available through Coroutines. So the question is: Will Loom make Coroutines obsolete, catapulting Coroutine code to the realm of legacy from one day to another? Or, in other words, will Java gain a significant advantage over Kotlin once Loom is final?

In this talk, we will try to answer these questions. Starting with a global introduction to how Loom achieves lightweight concurrency, I will compare essential characteristics with Coroutines, such as suspend calls, structured concurrency, and context propagation across Threads. Live-coded examples will illustrate the pros and cons of the different approaches and give you a better understanding of the underlying concurrency concepts. Moreover, light will be shed on whether it makes sense to combine Loom with Coroutines. At the end of the talk, you have gained a good understanding of what Loom will mean for Java and how it will impact Kotlin, so that you are ready for the next ‘big thing’ on the JVM.

Kotlin multiplatform + Domain models = ❤️
Nico Krijnen

In most of the applications we write, most of the domain model with all the crucial business logic only lives in the backend to ensure consistent behavior of a system. But with Kotlin multi-platform, that same domain model can suddenly also be used in your user-facing applications.

In this talk, we will look at what that means for the applications you build. What does your code look like when you share your domain model? How do you ensure that that domain model is re-usable? What kind of trouble can you run into and what techniques can you use to avoid that trouble? And how does the ability to use the full domain model benefit the user experience? And last but not least, how can your organizational team structure make this way of working a huge success or a road towards disaster?!

Please register yourself on our Meetup page