Re: 2.7 thoughts: common well-architected object model

Nick Piggin
2003-10-14T06:01:22Z

retu wrote:

>// these ungeneric interfaces will kill. Right now
>it's a
>{/usr/local/,/usr/bin/,/usr/..}NameYourClassLibrary_empty.
>Below a list pasted from the .net namespace with many
>dozens of classes covering everything from io to
>drawing.
>
>They _appear for the most part to be consistent
>wrappers to underlying existing APIs (including some
>for >kernelspace< to userspace), are quite well done
>although a little on the heavy side. I've not seen
>Nextstep for years but this was a very good design
>along the same lines and much thinner (implemented to
>fly on 20MHz+ 68040s).
>
>Hence, what would be needed is in the first place a
>component model (well architected - thin - efficient)
>that would allow folks to populate the other areas
>successively. Replicating .net for licensing and
>efficiency reasons (Linux ought to scale to HPC
>levels), broadening some application class library OR
>architecting something without the kernel in mind is
>not it I believe. It's gotta come from the core, have
>the ingenuity that leads others to build on it and not
>start with a disconnect (to the kernelspace that is).
>
>If there are multiple sets of classes for e.g. 2D
>drawing then so what as long as they use the same
>Linux component model (which has yet to be defined or
>even a grain of consens found that it is necessary in
>the first place).
>
>Now here's the competition:
>

Retu,
I don't mean to sound rude, but you're mail is somewhat incoherent.
Also, you
have not addressed some people's questions. This really frustrates
people and
that can cause a potentially useful discussion to go nowhere.

What you need to do is raise or elaborate on _one_ idea per paragraph, have
some sort of introduction or overview and logically structure your argument
from there, stop using parentheses, stop using marketing buzzwords and most
of all, explain specifically WHY your ideas are better than what is already
available in Linux. Don't keep repeating how other operating systems do
things
unless you back it up with an analysis of WHY it is better than what Linux
has.

Best Regards,
Nick Piggin