Hello everyone,
A bit about me then the question: ...
# springp
Peter
10/22/2019, 6:01 PMHello everyone,
A bit about me then the question: I use Kotlin almost 5 months now. I have been programming for about 2 years total(1.5 year trying to learn Java - spring, 5 months professionally). Currently I am using Kotlin with Spring Batch & Boot.
All this time I have been skipping Concurrency "for later" and I think the time has come now. I am thinking If you guys as most experienced individuals, would suggest I skip Java concurrency and dive directly to Kotlin concurrency/coroutines?
Will I miss "important background" if I do that, or is it completely normal to start my journey with kotlin? Thanks.
p.s. Sorry If this should go to #getting-started. I ll post there as well.
x
xenoterracide
10/22/2019, 8:17 PMyou should also understand what happens if you use a library that spawns threads in a coroutine, and why… the question of why do we have 16 worker threads… well because you spawned 4 threads from something that already was running across 4 threads
xenoterracide
10/22/2019, 8:17 PMI would say it’s good to understand threading at a conceptual level
a
alex
10/22/2019, 10:31 PMIt's not like coroutines and structural concurrency are something orthogonal to old-style concurrency, it's an abstraction based on it. Pick what you think will benefit you right now, then keep pace and learn missed stuff. You'll need both eventually.
4 Views