Daniel,

> 	And that's my argument. To make it easy in eToys 
> requires ease in Morphic, to make it easy in Morphic
> requires restructuring morphic, 
> which may break eToys, which requires fixing eToys....
> 
> 	You can't fix eToys w/o fixing morphic. It's too ugly. 
> 
> 	eToys is neat, but it should not be the only interface 
> to the system. A simpler interface to morphic makes a simpler
> job of supporting and expanding eToys scripting...
> 
> 	There is a LOT of ugly glue between morphic, eToys, 
> etc. It needs to be cleaned out, simplified, etc...

I never claimed the opposite (read my messages carefully). It was starting
this process with the notion of "having two worlds" - one for the
programmers and one (or rather: none) for scripting users that upset me.

Cheers,
  - Andreas