Looking forward to it, but currently we are using Akka, which also allows a huge load of actors working at the same time with only a few real threads underneath it - and Akka offers a cleaner programming model than threads, to be honest.
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.)
I totally agree, I regularly use both Akka and standard Java threading depending on the service, and I find the Akka model is much simpler to conceptualize, and is biased towards safety of shared state.
No idea why you're getting downvoted, that seems very reactive to me ;)
please stop spreading non-sense, the whole reactive model can't die soon enough, to me feels like scrum, pump-up up but course sellers and consultants, the performance benefits in real world are small and development experience is a nightmare, I may as well do callback hell in javascript.
You might be slightly confused here. Akka Actors is an actor framework, not a reactive one. Reactive programming can be used with actors, true, but most often, it isn't. And actors are much, much older than reactive programming. In our case, it's not anything reactive, just actor based programming, which is a very nice model that increases encapsulation and enforces it much more than standard OOP.
(Of course, you can use parts of Akka Streams in a reactive way, but that's only one option for one specific side library of Akka.)
Well, depends on what you mean by reactive framework; if it's any framework that makes creating a reactive system easier then Akka is certainly a reactive framework - after all, its creators are also the co-authors of the Reactive Manifesto and if you've taken any Lightbend Academy courses then you know they like to point out Akka's reactive roots. However, if by reactive framework you only mean reactive streams framework then yeah, that's just the Akka streams.
12
u/Iryanus Aug 02 '22
Looking forward to it, but currently we are using Akka, which also allows a huge load of actors working at the same time with only a few real threads underneath it - and Akka offers a cleaner programming model than threads, to be honest.