<https://www.infoq.com/presentations/continuations...
# coroutines
s
https://www.infoq.com/presentations/continuations-java/ Most of the talk is about Fibers, Continuations, Structure Concurrency, Sequences, etc.
r
So wait, is it that Oracle and Jetbrains are working together. Or is Oracle just using there copy cat skills?
Like in there newest iterations, have all been features that kotlin already had. sealed classes, var keyword ect
s
The concept of Continuations is old (from the 50s). Hard to say who copied who:-) Also, it seems that project Loom would like to make all code 'suspendable', yielding is possible from any place in the code (no need for
suspend
or likewise keywords).
2
n
i am really looking forward to seeing if coroutines will be able to piggyback on loom and make ue of all the improvements in the jvm oracle has made
s
coroutines will be able to piggyback on loom
I like coroutines, but just curious, once Continuations and fibers are available on JVM, why you need to use coroutines? All JDK I/O and java.util.concurrent APIs will become non blocking in Fiber(ie, fiber blocking) and also fibers doesn’t suffer from colored function issue (required bridge functions to move from sync to async) . Also, all the blocking JDK libraries will work without any modifications on Fibers (which is not the case for coroutines). It will really difficult to sell coroutines on server side once java get Fibers.
o
I'm not sure that not having bridge functions between sync and async is a bad thing, though. I mean, JS lets you mix and it feels like a serious pitfall there.