Hi guys! Please first first have a look at that simulation: http://www.youtube.com/watch?v=EmMY1nq_tgI Surprisingly the architecture of pharo looks very much this. Message sends, "information flow" through a dynamic ambience of "living objects" cause serious "hangs" Unpredictable traffic jams occurr, depending on load, e.g. Seaside, during GC, Image sync, subtile timeouts or countdows, waiting for resources to be freed, network timeouts, database lookups, e.t.c. Those can much easier be identified, when you downclock your machine to good old 50MHz of ancient times of squeak and develop/profile then. Design flows pretty soon become visible then, that are not visible when you proudly use always the newest Apple machine for development.
From advanced Software architects of a new old Smalltalk OS i expect to know about such dynamic phenomenons, having deep insight into analytically identifying such normally difficult to indentifying problems, that always should be part of TDD ...
Tnx for reading and understanding. Have fun! Guido Stepken