npm83
- 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?
I really like the idea, and reading through comments this question came to my mind.
Names are important for us. They synthesize what a "thing" is, and they help us organize knowledge.
So even though it might be true that for computers names are not that important (i can describe what i want), i believe they are for us, humans, when trying to understand a given system.
We grow systems both for humans and for computers.
What's your take on this? How would you find balance between the two?
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?
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.
Even though is "old", I find it extremely valuable for learning to think and reason in a pure OO fashion.