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.

tweet 1788085182366409028

Now a big misunderstanding that required explanation:

tweet 1786273236239442067

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:

tweet 1783110094814605711

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

tweet 1784796817319690435

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

tweet 1787346616304742686

A humorist ending of this series:

tweet 1787830156565893450

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.

tweet 1772215098238484683

tweet 1772888535747760169

tweet 1775050279958028619

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.

tweet 1788433731151167941

tweet 1784885439909745086

tweet 1787749571541573987

tweet 1783750561822658809

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:

tweet 1788433731151167941