Another case of reinventing the wheel and calling it something new. This is just a reimplementation of what used to be called the "blackboard architecture". ht

Another case of reinventing the wheel and calling it something new. This is just a reimplementation of what used to be called the "blackboard architecture". http://en.wikipedia.org/wiki/Blackboard_system http://en.wikipedia.org/wiki/Blackboard_system I don't see how broadcast is more "reactive" than singlecast. And the solution to tight coupling in actor systems has already been thought of - it is a message broker. This is just an actor system where every actor shares a single message broker. Its cool that you built your own system for actors, and I certainly wouldn't discourage people from reimplementing something for the sake of learning, but every criticism you have of traditional actor systems is inaccurate. Strangely enough, you criticize Orleans in particular, which is especially good about tackling the coupling problem by making actor references virtual. "Perhaps the central problem we face in all of computer science is how we are to get to the situation where we build on top of the work of others rather than redoing so much of it in a trivially different way." -Richard Hamming