Smalltalk is very long in the tooth these days, but it is still "rather object-oriented in good ways".
Erlang and its derivatives are fun and good to help that kind of thinking.
Even though is "old", I find it extremely valuable for learning to think and reason in a pure OO fashion.
I assume your are talking in the lines of "call by meaning" when you mention that names are relatively local, right?
As for "send processes rather than messages", isn't that what objects are about?
I mean...sending the real thing, not just "data" as part of a message. That reminds me of the Burroughs 220 and "delivering video + codec together" example you mention in your talks.
The modularity thing sounds pretty much to well designed objects to me, but it seems that you're trying to make a difference between that and processes.
What do you have in mind or, better said, which could be a concrete example of it?
- what if we cant send processes instead of messages? - what are we missing? - which things cannot be done?
Pretty much what we have nowadays.
I find it hard to understand how sending processes (assuming they're not only objects but the context in which they live) help scaling the system.
Which example are you thinking of, that i cannot because I'm lacking this idea of processes rather than messages?