Hi @Kotlin by JetBrains, Glad to reach you! I really excited about Coroutines. In that, I'm having one confusion. it's very crucial for me please let me clarify in it. If I'm having the CoroutinesScope(Dispatures.Main) and inside that I'm launching 1000 coroutines. in that case its really can archive the 1000 concurrency? The cause of the question is, anyway the UI Thread always runs in the Manner of sequentially right. then how it really archive or update to the UI in parallel manner?
Asynchrony does not necessarily mean parallelism. Dispatchers.Main is single-threaded, hence, your coroutines gonna run sequentially: one suspends or finishes-the other one starts or resumes.
Can someone explain what the added value is of using the coroutines mechanism in the parsing library? I could not really understand this portion. Is it more efficient? Good talk overall.
I guess the idea was to use coroutines while also avoiding exhausting compute resources when parsing and keeping the symbols. But is not clear to me if that was intended too in the presentation.
I have been working as android developer for more than 6 years. but working on kotlin for architectural changes feel very complex. Any suggestions for books or sources?
parser combinator looks cool af
Thank you so much for this video! It was super useful! 🙏
Great talk!
Hi @Kotlin by JetBrains,
Glad to reach you!
I really excited about Coroutines. In that, I'm having one confusion. it's very crucial for me please let me clarify in it.
If I'm having the CoroutinesScope(Dispatures.Main) and inside that I'm launching 1000 coroutines. in that case its really can archive the 1000 concurrency?
The cause of the question is, anyway the UI Thread always runs in the Manner of sequentially right. then how it really archive or update to the UI in parallel manner?
Asynchrony does not necessarily mean parallelism. Dispatchers.Main is single-threaded, hence, your coroutines gonna run sequentially: one suspends or finishes-the other one starts or resumes.
Can someone explain what the added value is of using the coroutines mechanism in the parsing library? I could not really understand this portion. Is it more efficient? Good talk overall.
I guess the idea was to use coroutines while also avoiding exhausting compute resources when parsing and keeping the symbols. But is not clear to me if that was intended too in the presentation.
I have been working as android developer for more than 6 years. but working on kotlin for architectural changes feel very complex. Any suggestions for books or sources?
One option is looking for open source applications and collaborating to the project to learn to do things in a different way.