I really appreciate this Project Loom piece, both for the good things it suggests about where the JVM is going, and for making a clear case that M:N threading is the right thing for most platforms. http://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html …
-
-
Replying to @samth
Ooh! One thing that's interesting about this design is that it pins a virtual thread to an OS thread whenever there's a mixed stack (JVM / JNI / JVM). Part of the design is that mixed stack are rare, so it's okay to pin threads.
1 reply 0 retweets 1 like -
Replying to @asajeffrey @samth
This is quite different from my experience with Rust, where (at least in Servo) pretty much all stacks are mixed Rust/C/C++, and quite a lot are mixed Rust/C/C++/JS.
1 reply 0 retweets 0 likes -
Replying to @asajeffrey
Is that because Servo is a mix of existing components and new ones?
3 replies 0 retweets 0 likes -
Replying to @samth
Some of it is Servo-specific (most Rust programs don't have a JS engine) but some is that Rust's ecosystem includes a fair number of crates that are thin wrappers round a C/C++ library.
1 reply 0 retweets 1 like -
Replying to @asajeffrey @samth
My guess is that Java's ecosystem has a lot more pure-JVM libraries.
1 reply 0 retweets 1 like -
Replying to @asajeffrey
I agree that there are definitely contexts where making concurrency more expensive to make ffi less expensive is the right trade, but I think most platforms are not in that situation.
1 reply 0 retweets 0 likes
I mostly see it as socket servers vs. other apps.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.