[ChrisRus]

Note that the idea here is sound; identify and specify the roles of various actors in detail specifying explicitly that they are not actual _classes_. Effectively, this is high-level block diagram and there's every reason in the world to have that clearly defined before actually building a system.

But, then when you go to actually implement and testing something designed this way that's non-trivial. That's the point where I am arguing that OOP should not be manner in which the implementation is expressed because the paradigm is optimized for organizing functions that operate on common data context. But, not for organizing actors that must share data and carefully coordinate the which and in what order functions are applied to modify that data.

[andrekandre]

> But, not for organizing actors that must share data and carefully coordinate the which and in what order functions are applied to modify that data.

you mean... the actor model?!

[dmux]

>...and in what order functions are applied to modify that data.

Is this solved in a better way using other paradigms?