I've been thinking about why, while I've been inte...

# coroutines

[jmfayard]

I've been thinking about why, while I've been interested about couroutines since kotlin 1.1 came out, I have been reluctant to actually use them in any of my projects yet.
It's not because I'm concerned about the maturity of the libs.
It's not because "they are still experimental", while I could use this lame excuse if asked out of the blue.
It's not because of the documentation, the documents and talks from @elizarov are great
It's that I remember when I first rushed to use Promises (in JS) then RxJava in my projects, I didn't have the practical experience to use them correctly and made a LOT of mistakes
Coroutines do seem easier to get right, but asynchrononicity is hard no matter what. I have no practical experiences with the style of programming with channels and actors for example.
So the real issue is that I lack a safe playground where I could practice all these new toys,
hopefully not only with "delay()" but also simple UX, DB and network stuff.
so the TLDR is that having and completing a kotlin #koans for coroutines would boost my confidence in my own ability to use them correctly!

[satejs]

Coroutines definitely make it seem a lot easier. I guess the way to go is experiment with them, with your current setup. My team has moved our experimental setup to production after some tests, and Kotlin with co-routines is performing well for us!