These are chat archives for akkadotnet/akka.net
winforms/wpf/asp.net require synccontext but only for some special cases where you want to run in that ui thread
(async/await) they really make it a lot harder to write clean actor code that complies with the basic concurrency restriction imposed by Akka actors
I think we concluded that it was inherently unsafe because if the continuation is "never" resumed, the actor is effectively dead and its mailbox will continue to pile up. Pausing processing is anti-responsive.
he said then
There is a compromise that is possible, though: enqueue incoming messages locally until the continuation has been resumed and completed (so that users are not surprised) until the local queue is full, at which point the actor fails. This places a limit on the non-responsiveness while not breaking semantics.