06/07/2017, 5:51 AM
@groostav Coroutines make async logic simpler to express. To get benefits over other approaches from coroutines, your code has to have some suspensions (waiting for network IO, etc). You can do all the other stuff with coroutines too by simply replacing threads with coroutines, but you will not get any saving neither in terms of code size, nor in performance. In particular, parallelising CPU-bound workflows of the type that Mike shows there falls into that category.


06/07/2017, 5:13 PM
elizarov: I was thinking more about getting work on and off the UI thread, which I think current coroutines are pretty good at (read: the code that does it should be fairly expressive)
Maybe I'll clone the repo and see what it looks like with 1.1