it's exposing many of the syscalls into relevantuser-space objects which makes the other OSs approachneat. Coming from the kernel an outline of a commonobject model should be suggested which is thenactually populated and refined futher by e.g. the GUIfolks.

The other way around has shown not to work with themany application-designed component frameworks outthere. In the other OS you'll be able to do things inI/O, process, GUI, data access etc. in a quite similarway. The current permutation in Linux for puttingtogether an application is staggering, which can forcepeople to use the lowest common denominator - likelibc.a ;) - it's actually not funny.

A core component model has to be defined by the kernelgroup and then trickle upward. That's the only waywhere you can sufficiently design in performance andsecurity(*) considerations which I agree should allowLinux to scale as well as it does.

(*) good example for the opportunity in leaping theother OS here: there is another big void in a soundsecurity component properties right now. COM+ hasquite a bit in it, but there is much more which couldbe done and people are keen on it. Another item whereLinux could start to define the envelope.

--- Valdis.Kletnieks@vt.edu wrote:> 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.....>