Re: 2.7 thoughts: common well-architected object model

Valdis.Kletnieks
2003-10-11T17:38:17Z

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Sat, 11 Oct 2003 10:13:55 PDT, you said:
>
> unfortunately it's rather a jump into elegance. The
> other OS component model is quite well architected.
> Hence what's needed is _a similar architecture effort
> which may _abstract many things in the beginning to be
> filled in later. Ther's a dire need for a sound and
> similarly elegant (or better) model.

Two words: "syscall interface".

Most of what you're blathering about needs to happen in userspace.

If there's disagreement over what GUI style to use, the kernel is
NOT going to provide any guidance. KDE versus Gnome versus the
other 23 window managers - that's all userspace. The reason there's
25 window managers is because 25 sets of people had *different goals*.

The kernel wisely stayed *OUT OF THE WAY*.

With a single common object model, Linux can push the envelope in ONE
direction. Which is why That Other System scales so incredibly well from
a Zaurus to a 128-CPU NUMA box, handles different GUIs for different goals,
and all the rest of that.....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]