I'd like to add to the desiderata:

 - Persistent immutable module versions.  If a program declares the version
   of each module that it depends on, it should be possible to load the
   correct dependencies and have the program work.  It should NOT be possible
   to change objects in these modules without first explicitly creating a 
   mutable copy.

 - Co-existence of module versions within an image.  If programs A and
   B depend on different versions of an object C, it should be possible to 
   load and invoke both versions without conflict.

Dan Ingalls wrote:
> First of all, as I put in my original message, we have a few desiderata that seem to meet with general favor:
> 
> 	A minimal kernel for the support of modules and
> 		inter-module dependence within the image
> 
> 	The ability for weekend hackers to write simple
> 		programs as easily as now
> 
> 	A Squeak release that is well partitioned so that
> 		it can be easily built up from a small kernel
> 		and fairly easily reduced again to a small kernel
> 		[thanks to John S and the StableSqueak folks
> 		for their bold step in this direction]
> 
> 	We want this soon
> 		I'm thinking something to test this month
> 		and a modular Squeak release in September
> 		(easy for me to say ;-)
>