Dan Ingalls wrote:
<lots of good stuff snipped>

Dan,
one thing that I find missing in this list is
configuration management:
code gets changed.
So there is the issue of how to coordinate changes
that different people make.
One way to handle that is to partition the system,
in order to distribute "ownership" and reduce conflicts.
Also, I want to be sure that when I load a module,
I get the same thing I got last time, independent of
what is in the image before loading.
And I want to be able to keep the instances while loading
a different version of a module, so loading a new
version is different than uninstall old, install new.

And one thought about the complexity/filtering issue:
Even though the tools may be able to filter the
view of the system, the code is nonetheless there
and may affect the behavior of the system.
So filtering may lead to "what you see is not what you get",
so to say.

Just my 2c,
Thanks
Wolfgang