[Cuis-dev] which classes to have in Kernel

[sp at xeny.net]

Arg - sorry - I didn't finish my last sentence before posting!  The last 
sentence was meant to read:

If we have these three levels then we can be relaxed about moving things 
  that are not completely essential out of Kernel and into *either the 
middle class or non-Kernel classes in the minimal image*.


On 5/21/22 8:57 AM, sp at xeny.net wrote:
> I'm a newcomer to Cuis but I've been thinking about this topic a lot and 
> I have a concrete suggestion.  Please excuse me if I've misunderstood 
> anything about the culture of Cuis.
> 
> I think we need three levels of classes:
> 
> 1. classes in the minimal image
> 3. classes in ordinary packages
> 
> and, less obviously, in between those two:
> 
> 2. classes in packages that are expected to be the canonical classes for 
> widely-used functionality (unicode is a very good example).  This is 
> like the standard library in source-code-based systems, but since Cuis 
> is image-based it would make sense to leave these classes out of the 
> base image (or, almost equivalently, mark them in a way that makes them 
> easy to remove from the base image).
> 
> If we have these three levels then we can be relaxed about moving things 
> that are not completely essential out of Kernel and into the middle class.
> 
> Jason