2.7 thoughts: common well-architected object model

[asdfd esadd]

With due respect, what 2.7 really needs is a
consistent well architected _single component model.
Why it should be spawned from kernel development -
because coming up with a consistent one from higher
layers has shown to be difficult/futile/impossible. 

Many of the feature ideas listed are great but it's
rather back to architecture at this stage.

A consistent component model is needed on which people
can extend and Linux will lap the other OSs, otherwise
it will be rather difficult to
compete on the application side in the end (argument
will be: Linux is is difficult to program and has
flagrant duplication). There are many good component
models out there but the parallel re-implementation of
everything somewhat lacks cast.

So here is the feature request:

* a unified well architected core component model
which is extensible


- RETU 



__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/