I should also say that of course you can do all this stuff in Erlang alone. Or in any other actor system. But you'll very likely end up greenspunning yourself something very similar to what syndicated actors offer, once your actor system gets beyond a certain complexity level.

(I've also been thinking about implementing syndicated actors as an Erlang behaviour, to allow Erlang actors to peer with other syndicate actors. The process dictionary would be a nice place to put the dataflow variables; and I could abuse monitors to implement the automatic-retraction-on-termination feature...)