>[ ]  With classes you know where all the code is.  The Browser has all the 
methods.  The methods are layed out in a spacial ordering.  This is one 
way to remember how to get back to a piece of code.

For reasons of sharing and selection of inherited vs idiosyncratic 
behavior, in the authoring environment it is useful to keep 'parents' and 
'children' which allows for ST style hierarchy browsing.  As the heap can 
be scanned to get this infomation, one might consider this knowledge as 
cached to allow for 'tree shaking'/liposuction to reduce image size.

>The problem with prototypes seems to be one of self restraint... Perhaps we 
should offer the user the choice each time,..

I am definately all for helpful/supportive interfaces!

Cheers,
-Ken