The impact of coroutines on async computation
kotlindevelopment.com
The impact of coroutines on async computation
1–6 of 6 posts
Re: The impact of coroutines on async computation
#2A very promising library, although experimental. Even has Android-specific extensions (https://github.com/Kotlin/anko/wiki/Anko-Coroutines).
Re: The impact of coroutines on async computation
#3A very promising library, although experimental. Even has Android-specific extensions ( https://github.com/Kotlin/anko/wiki/Anko-Coroutines ).
Of course they have, it is maintained by JetBrains :D
Re: The impact of coroutines on async computation
#4What do you guys think about how it compares to Rx? There are opinions about they are on a different abstraction level so they don't compete with each other.
Re: The impact of coroutines on async computation
#5What do you guys think about how it compares to Rx? There are opinions about they are on a different abstraction level so they don't compete with each other.
I agree, coroutines is good for the simpler use cases, while Rx is better for composed transformations. Not sure about using coroutines in prod though, while still experimental.
Re: The impact of coroutines on async computation
#6What do you guys think about how it compares to Rx? There are opinions about they are on a different abstraction level so they don't compete with each other.
I agree, coroutines is good for the simpler use cases, while Rx is better for composed transformations. Not sure about using coroutines in prod though, while still experimental.
I’d definitely would wait for the non-experimental release, just in case.