Adrian Lienhard wrote:
> What I wanted to say is: lets identify what is most critical and 
> encourage people to work on this now, rather than talking about what 
> would be the perfect solution that solves all problem (although that's 
> nice too).

That's why I said "start here" ;-) There is a good list of things to 
choose from all of which are (in my understanding) necessary. If there 
is overlap with your (or anyone else's) needs, great.

> Of course, then, everybody has different needs (for example, it seems 
> you care less about speed, whereas I would rather like to have more 
> speed than having correctly working overrides because I can work around 
> the latter but not the former) but I have the impression that with some 
> concrete steps we could already go a step forward. Let's take the atomic 
> load. It seems it would solve a couple of problems (e.g., load order 
> dependencies, moving methods/classes between packages), no?

Depends on what you mean by "atomic load". If atomic means you load and 
compile everything, and when finished you install everything in one big 
become, then yes, this would fix many problems. If you mean "load 
packages together" instead of one after the other, then no, this wouldn't.

Cheers,
   - Andreas