Actually I was not familiar with Orleans until now. I think there's probably similar primitives you could build but from my quick 2s read they're solving a higher order problem. Additionally having written an actor lib in the past in .net, I can say they can't match rust for speed but they do have some nice syntax stuff with reflection we can't do.

So it's a tradeoff on stuff like syntactic sugar and speed imo

Orleans was born to support Halo's server backend and went from there, they know their stuff regarding performance.

> Orleans is used by Microsoft in Azure, Xbox, Skype, Halo, PlayFab, Gears of War, and many other internal services. Orleans has many features that make it easy to use for a variety of applications.

https://learn.microsoft.com/en-us/dotnet/orleans/overview

Until Ractor proves itself in similar workloads, it is a tiny bit more than syntax sugar difference.

I'll just say this, it's deployed in production scale at WhatsApp along side Erlang. Not as many services, but still serving the global user-base of WhatsApp. We have many services we've migrated to this where we had "hacked" together actor frameworks

Fair enough, then it is proven that it can handle the load.

Then there is the question about the features themselves, besides what any actor framework should provide as baseline.

Orleans is already on version 7.