Thoughts on the nature of programming...Asynchronous Events

Peter Crowther Peter.Crowther at IT-IQ.com
Thu Jun 24 12:56:52 UTC 1999


> Well each object would have some proximity factor to all other objects in
> the system.

What proximity factor, how set, how derived, how calculated?  Seems to me
the coupling is being arrived at by the back door of object positioning
within some multidimensional structure --- in the same way that one's head
is coupled by proximity to one's body.  If the two are separated in space,
the overall system fails catastrophically.  What's more, the coupling is
present at decreasing strength throughout the entire system.  Here,
affecting any one object potentially affects all other objects in the
system.  They're all married together --- for better or worse, richer or
poorer, in sickness as well as the undoubted initial health.

> If it worked, the browser would suddenly be much more robust.

No it wouldn't --- if it were written in this system, potentially moving or
otherwise operating on *any* *one* other object in the system would disrupt
the event propagation within the browser's own code.  The whole system would
be robust in the sense that *something* would keep happening, but you now
have the distinct possibility that the browser would fail due to editing the
'code' of an 'object' on the other side of the system.  Or you accept the
very non-Smalltalk idea that the browser is outside the system being
studied.

		- Peter





More information about the Squeak-dev mailing list