https://kotlinlang.org logo
Title
a

asad.awadia

12/28/2018, 5:40 PM
@elizarov why did kotlin not go the go route with coroutines and having a scheduler deal with moving things off onto other threads? Was the aim to give more fine grained control to the developer?
l

louiscad

12/30/2018, 5:52 PM
You're partly right regarding giving more fine grained control. Kotlin strives to be explicit. That's why you need to be specific about where a coroutine is launched, where you want to switch execution context (which is not just about dispatcher BTW), and that's why we have structured concurrency in kotlinx.coroutines.
👍 1
e

elizarov

01/06/2019, 9:51 PM
That. And we also needed to support single-threaded UI frameworks like Swing and Android.
👍 1