<@U2E974ELT> Ok great - I think this gives a gener...
# coroutiness
s1m0nw1
06/30/2017, 1:08 PM@elizarov Ok great - I think this gives a general idea of how coroutines really compare to threads, especially in terms of use cases. Maybe it's an idea to phrase something of this in the documentation? I'm asking myself if Java, given your definition, is much more inefficient than Kotlin regarding performing concurrent tasks, as most of the time threads are being used in those cases since no other standard tool is provided (let's forget about reactive stuff like Rx or vert.x for this). Is it correct to say, that usally threads are NOT what you should be using in Java actually?