So we're off topic of the architecture of this case.
Note the change in the subject line to stop recording in the
case directory.
> 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"?
IMO, that's a second order tricky. IMO, the first order
tricky is defining A, B and C such that given some component,
it get's categorized into A, B or C (presuming that they are
disjoint, which I don't believe they can be).
> 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".
+1
Gary..
