Garrett D'Amore wrote:
> bloat
Think of the compiler world, where there are the concepts of
"part of the compiler", "part of the hosting OS", "add-on
features and libraries" and "customer provided stuff".
In the OS world, this concept might result in the following
classifications:
A) "part of the core OS",
B) "part of the WOS that collects around that core",
C) "add-on features and libraries" and
D) "customer provided stuff".
If I hear you correctly, Garrett, you are saying
Don't simply dump more and more stuff into the "A"
bucket, as it is already too full of bloat.
and, more importantly, you are NOT saying
Can't be part of "C" or "D".
I don't think anyone will argue with this - the undefined and
tricky one is "what should be in "B"?
I don't know *how* to produce "C" things, and I'll bet nobody
else does either, which may explain why things are being dumped
into "B".
-John
