@spierce7 this might be an example of part of what we spoke about 🙂

I still don't feel compelled to replace my RxJava code with coroutines. Give me a higher abstraction like RxJava that is backed by coroutines, and I'll be happy.

I think people still don't get that coroutines is a totally different approach, people are just using coroutines, but still not benefiting from their full potential... It takes a while to grasp, and it certainly doesn't cover all rx use cases, but when it does, if used properly, the advantages adds much bigger... The article is partly showing to start getting into another mindset.

Rx and coroutines are not necessarily different, but rather complementary. Somebody just has to do the work to build an Rx implementation with coroutines. https://github.com/Kotlin/kotlinx.coroutines/blob/master/reactive/coroutines-guide-reactive.md

I agree @thomasnield, but I think you can't build coroutines code the same way you do rx. They're two worlds in that sense, but they can be complimentary.