He-Pin commented on PR #2156: URL: https://github.com/apache/pekko/pull/2156#issuecomment-3261715949
We are currently using Spring-Ai and MCP SDK at work, which are totally built the the reactor-core. I always wondered, why can't it be Pekko-stream. And nowadays, the virtual thread makes direct style programming possible, see how ox-stream and ox-actor are being implemented, yes, the blocking should be managed, but may not be a problem when you are running the actor/stream with virtual thread. There is a Jox library being implemented with pure java, so I think Pekko Stream should be quite simple and friendly for Java developers too. <img width="1213" height="507" alt="image" src="https://github.com/user-attachments/assets/d0ffe44f-46d2-4608-a3c5-39e63f037c92"; /> This code is from a system where we leverage pekko stream to do translation for Taobao English, you can see the long ``` withAttributes( ActorAttributes.withSupervisionStrategy( (org.apache.pekko.japi.function.Function<Throwable, Supervision.Directive>) param -> { log.error("AsyncOvsTranslator error", param); return (Supervision.Directive) Supervision.resume(); })) ``` In Reactor-core will just be an `onErrorContinue`. -- 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: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
