News for hackers. Stuff that matters.

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

Re:Project Loom: Fibers and Continuations for the Java Virtu... by s_kilk on Wednesday November 01, 2017 @10:30AM (#15601421)
Would this mean having something in Java like the M:N thread model we see in Go, Erlang, and such?
[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by peoplewindow on Wednesday November 01, 2017 @12:58PM (#15603206)
Yes, it would.
[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by dboreham on Wednesday November 01, 2017 @01:13PM (#15603366)
Again. Since it has this long ago, and long ago removed[1] when folks realized that OS-native threads are the way to go if you have them.

[1] https://en.wikipedia.org/wiki/Green_threads#Green_threads_in...

[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by dragonwriter on Thursday November 02, 2017 @10:04AM (#15610453)
Old Java threads were 1:N, not M:N, and were instead of rather than in addition to support for 1:1 native threads. Having the choice between 1:1 and M:N both available on the platform is better than being locked into 1:1 or 1:N (or even M:N.)

What is offered here is strictly better than the current or previous state.

[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by wtetzner on Wednesday November 01, 2017 @02:28PM (#15604110)
> when folks realized that OS-native threads are the way to go if you have them.

Well, it depends on what you're trying to do. Having the option of using either is preferable.

[ Parent | on HN ]
Re:Project Loom: Fibers and Continuations for the Java Virtu... by dullgiulio on Wednesday November 01, 2017 @05:20PM (#15605573)
Absolutely, especially if the lightweight threads are implemented on top of OS threads, which is not what was done with Green Threads.
[ Parent | on HN ]