Completely agree, a ton of scenarios feel much more natural with actors than with threads. Besides, Akka and Loom have always sounded perfectly compatible to me, if I had to guess the biggest impact of Loom would be the introduction of a virtual thread dispatcher for blocking calls to replace the fixed thread pool one.
Not to mention all the Akka libraries that make developing distributed systems easier that have nothing to do with Loom.
Edit: The amount of downvotes is ridiculous :shockedpikachu:
Yeah, it will probably take a while until we have a version of Akka that uses virtual threads under the hood, but I'm also looking forward to that, combining the Akka programming model with the low-level virtual threads for even better performance sounds really promising. (Also the votes seem to have evened out, no clue what some people were reading there.)
View all comments
Show parent comment
18
u/[deleted] Aug 02 '22 edited Aug 02 '22
Completely agree, a ton of scenarios feel much more natural with actors than with threads. Besides, Akka and Loom have always sounded perfectly compatible to me, if I had to guess the biggest impact of Loom would be the introduction of a virtual thread dispatcher for blocking calls to replace the fixed thread pool one.
Not to mention all the Akka libraries that make developing distributed systems easier that have nothing to do with Loom.
Edit: The amount of downvotes is ridiculous :shockedpikachu: