mdedetrich commented on issue #611:
URL: 
https://github.com/apache/incubator-pekko/issues/611#issuecomment-1703770379

   So one thing to note here is that if we use Loom unless we can put the 
functionality into another artifact we are basically going to be forcing users 
to use the newest JDK. There are hypothetical solutions for this, i.e. 
https://github.com/sbt/sbt/discussions/7174#discussioncomment-5288982 would 
allow us to release pekko with class filees that are specific to a JDK allowing 
users of Pekko to automatically get the features of Loom if they are using 
latest JDK will still supporting older JDK's
   
   One other thing to note is that at least if we are talking about 
performance, I am not entirely sure that Loom is going to give us benefits. 
Actors is another design to solve some of the problems that Loom does, i.e. the 
messaging protocol of actors is immutable data which is one of the reasons why 
they perform so well and Loom isn't really going to get us much here given that 
logic in Actor's are guaranteed to execute on the same thread (loom gives us 
performance benefits when context switching).
   
   Loom can provide performance improvements if we are talking about `Future` 
comprehension, but this is kind of orthogonal to Pekko (i.e. we would get these 
improvements automatically if someone was to provide an `ExecutionContext` 
backed by Loom) and I would presume a better way to solve this problem is to 
just provide these `ExecutionContext`'s for Pekko as a separate artifact (even 
library) for the Pekko users that use Loom.
   
   In essense Loom is probably more useful for those who are stuck on blocking 
IO/logic in Java world or use of effect IO types such as Cats Effect/ZIO


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to