Project Loom: Fibers and Continuations for the Java Virtual Machine

Post by geodel » Wed, Nov 01, 2017, 4:22 PM UTC

djb_hackernews wrote: post #8

I skimmed the article but this seems heavily influenced by Quasar http://docs.paralleluniverse.co/quasar/ but doesn't make any mention of it. I have some experience with it and I found it to be a very well designed and documented API. I hope to see it in the JVM someday. The person behind it is pretty active online and does some other interesting things (the TLA+ subreddit), not sure if they are an hn reader but I ho…

Post by peoplewindow » Wed, Nov 01, 2017, 4:58 PM UTC

s_kilk wrote: post #2

Would this mean having something in Java like the M:N thread model we see in Go, Erlang, and such?

Post by dboreham » Wed, Nov 01, 2017, 5:12 PM UTC

zbentley wrote: post #5

This is an excellent introduction not only to work being done on the JVM, but on some of the implementation challenges of userspace concurrency/greenthreads and M:N scheduling in general. The detail, nuance, and humility present in this article give me some hope that pathological misbehavior of other M:N scheduling models (see Bryan Cantrill's rant/paper about this for more info) may be avoided if something like that…

Post by [deleted] » Wed, Nov 01, 2017, 5:36 PM UTC

dboreham wrote: post #15

zbentley wrote: post #5

This is an excellent introduction not only to work being done on the JVM, but on some of the implementation challenges of userspace concurrency/greenthreads and M:N scheduling in general. The detail, nuance, and humility present in this article give me some hope that pathological misbehavior of other M:N scheduling models (see Bryan Cantrill's rant/paper about this for more info) may be avoided if something like that…

Executive summary : It will probably all end in tears. It would be nice just to have TLS that works with NIO[2].

Post by tomp » Wed, Nov 01, 2017, 5:49 PM UTC

vvanders wrote: post #14

Pretty disappointed that continuations won't be able to yield a value(s). That was one of the most powerful things about Lua's coroutines. Back in games we'd use the yield value as the number of frames to skip before rescheduling giving a really nice coarse grained control over coroutine execution. It also opens up lazy sequences and all sort of other really useful things.

    produce 1
    fiber sleep 100ms