There has been wuite a bit of talk about this over the last few days.

You might want to check out the threads:

'visibility" of class object in favour of a global context'
and
'the monopoly of classes'

before jumping into the fray :)

Julian

JOEL SHELLMAN wrote:
> I took a look at the Object type today and was startled to see how many
> methods there are defined on it. Especially such specialized things as
> morphs. Why should the Object class know anything about morphs, SUnit,
> skins, and collections?
> 
> I assume that nearly everything subclasses from Object, correct? Why is
> Object so huge?
> 
> And I guess what I'm really asking is... "should" Object be this huge, 
> or
> has it just become such from poor design or some other reason?
> 
> Thanks,
> 
> -joel shellman
> 
> 
>