>MH> I'd say this means the desire is to keep the compilation speed whithin
>MH> reason but not as a really major design goal.
>I think it depends on the person. Some people want a MLM that's easy to
>install and that has lots of features. Others want to push huge volume
>through with few frills. A single MLM can't play both roles effectively.
Isn't the best way to do this is to try and have a configuration stage that
includes/excludes key features from the run time version that get's
where "key features" = possibly unused features on a given install that
have a not insignificant performance hit