This seems to be used at Meta: "Ractor had a session at RustConf’24 about how it’s used for distributed overload protection in Rust Thrift servers at Meta."
Their presentation [1] contains a few slides with the motivation for this framework (they have existing Thrift services in C++ and Python, and want to start using Rust too) and why actors (answer: they scale better than a naive solution?). Also a slide "why a new framework" when so many already exist for Rust. (Answer: many are dead/unsupported, are too far from Erlang principles, not flexible enough, or use custom runtimes while ractor builds on Tokio.)
If you've ever used an ML descendant you'll miss sum types wherever you go. If you've ever used Erlang you'll miss the OTP actor implementation wherever you go.
Yeah I do lol. It was the big motivation since we were writing more and more rust and missed the concurrency model. Please feel free to ping me for any further questions
It's come a long way since it started and I'm thrilled I can talk about it publicly now and it's usage at Meta (some at least lol).
