Hi are Coroutines days numbered now that LOOM is o...

# coroutines

[Tower Guidev2]

Hi
are Coroutines days numbered now that LOOM is on the way?

[reformator]

Coroutines are still necessary for Android, native and JS. And Loom is in preview so far.

[kevin.cianfarini]

Also coroutines aren’t exclusively useful for IO related things (which loom is). Things like bridging callbacks to a flow to ensure cleanup happens properly will not be obviated by loom.

[reformator]

I don't agree, everything which can be done using coroutine can be done with Loom API. Cause Loom is not just virtual threads, it's also coroutines implementation on JVM.

[reformator]

For example, it's usage of Loom for Swing UI operations. https://gist.github.com/Anamorphosee/9a6436b9093b597ea69be405443f33ad

[kevin.cianfarini]

Interesting! TIL, thanks for sharing.

[CLOVIS]

Coroutines are also not just concurrency. See the sequence builder for example.

[kevin.cianfarini]

and deeplyRecursiveFunction

[reformator]

sequence can be implemented with Loom.

[CLOVIS]

@reformator of course, but it will be extremely slow.

[reformator]

why?

[CLOVIS]

Because virtual threads create a new execution context, the sequence doesn't, it just exploits the state machine generated by the compiler

[CLOVIS]

(I'm not an expert, I could be wrong on this, but I understood Loom as purely "cheap-threads" oriented whereas suspend doesn't require threads at all)

[reformator]

Which Loom can do either. Give me 15 minutes, I'll write simple Sequence with Loom.

[reformator]

No, Loom is not just virtual threads.

[reformator]

Here is sequence with Loom
https://gist.github.com/Anamorphosee/017b2475f8b3e797a5897077da7e8143

[CLOVIS]

Nice, thanks 👍

[streetsofboston]

https://youtu.be/1qezCNVWpHc▾

[Arjan van Wieringen]

Kotlin isn’t only JVM. So coroutines are here to stay