Kotlin bites on X/Twitter 3

Time for another edition of Kotlin tweets, this one filled with goodies, as @MarcinMoskala got really active in recent weeks.

Let's start this collection from some essential knowledge about nullability in Kotlin, and how it changed our industry.

Now a big misunderstanding that required explanation:

Feel warmed up? So let's move to the topic that fired up our community: the discussion about IO dispatcher.

Everything started with this bite, that so some seemed obvious, but for others was a revelation:

After that, Marcin added more context. Explained why IO is limited:

And showed why we should not use it directly, but create limited dispatchers based on it:

A humorist ending of this series:

In April, Marcin published a collection of very interesting challenges related to Kotlin Coroutines. They already have solitions on responses, but you can still try to solve them yourself.

We were also active in last weeks. We presented a small collection of Kotlin optimizations. Those built into language, and those that are just good practices.

I hope you liked this collection. If you did, let us know on... X/Twitter! If you want to see more, follow @MarcinMoskala and @KtAcademy on X/Twitter.

For dessert, here is an interesting use-case for async: