News for hackers. Stuff that matters.

A comment on Project Loom: Fibers and Continuations for the Java Virtual Machine. Parent comment

Re:Project Loom: Fibers and Continuations for the Java Virtu... by relics443 on Wednesday November 01, 2017 @10:58AM (#15601692)
My understanding of all these projects is that you have to change your style of coding / have more complex APIs, or they're just syntactic sugar over heavyweight threads.

What loom seems to offer is the best of both worlds; going back to writing simpler code (e.g. regular "blocking" io code) while scaling much better.

[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by _Codemonkeyism on Wednesday November 01, 2017 @03:49PM (#15604842)
"blocking" io code would be blocking.

Every IO library would need to migrate to something non blocking. This might happen with some - currently some use Netty and NIO - but e.g. JDBC drivers are synchronous.

[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by relics443 on Thursday November 02, 2017 @01:26AM (#15608051)
I believe the article mentions making the java.io package aware of fibers.
[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by _Codemonkeyism on Thursday November 02, 2017 @05:34AM (#15608949)
Yes you're right, though it would be a miracle - I hope for it ! - if this can be done without changes to existing code.
[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by SureshG on Tuesday November 07, 2017 @04:29PM (#15647834)
> have more complex APIs, or they're just syntactic sugar over heavyweight threads.

I am pretty sure that's not the case with Kotlin coroutines :)

[ Parent | on HN ]