Every developer on the planet, both Java and .NET, needs to stop and think about ways to focus on messaging, even between classes, rather than straight method calls, not because this is the silver bullet that solves all your concurrency issues, but that in certain cases it can certainly reduce them.

There's another interesting tie-in. I was reading Carlos' post on designing usable API's, which referred to the Curried Object pattern. The Curried Object pattern feels very Actorish to me. The notion of returning an appropriate intermediary is very much like the become step of an actor computation. Of course, the notion of an object with just the right set of methods (my interpretation of "an appropriate intermediary") feels sort of like a capability.

As you can see, a number of things have been swirling around in my brain...