mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: asdfd esadd <retu834@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: retu834@yahoo.com
Subject: 2.7 thoughts: common well-architected object model
Date: Fri, 10 Oct 2003 21:45:14 -0700 (PDT)	[thread overview]
Message-ID: <20031011044514.19799.qmail@web13005.mail.yahoo.com> (raw)

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

             reply	other threads:[~2003-10-11  4:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11  4:45 asdfd esadd [this message]
2003-10-11 14:30 ` Valdis.Kletnieks
2003-10-11 16:06   ` asdfd esadd
2003-10-11 16:48     ` Valdis.Kletnieks
2003-10-11 17:13       ` asdfd esadd
2003-10-11 17:38         ` Valdis.Kletnieks
2003-10-11 17:56           ` asdfd esadd
2003-10-11 18:20             ` Mark Hahn
2003-10-11 18:13       ` Zwane Mwaikambo
2003-10-11 23:33         ` J.A. Magallon
2003-10-11 17:00     ` Scott Robert Ladd
2003-10-11 17:57     ` Kenn Humborg
2003-10-11 18:34       ` asdfd esadd
2003-10-11 18:46         ` Valdis.Kletnieks
2003-10-11 19:01         ` Kenn Humborg
2003-10-11 19:11           ` retu
2003-10-11 19:25           ` viro
2003-10-12 11:59         ` Jamie Lokier
2003-10-12 16:04           ` retu
2003-10-12 16:44             ` Valdis.Kletnieks
2003-10-12 16:51               ` retu
2003-10-12 17:50                 ` viro
2003-10-12 21:52             ` Jamie Lokier
2003-10-12 20:21         ` Rik van Riel
2003-10-13 20:21         ` James Antill
2003-10-14  5:01           ` retu
2003-10-14  6:00             ` Nick Piggin
2003-10-14  5:31           ` retu
2003-10-14  6:05             ` Tim Hockin
2003-10-14  6:46             ` viro
     [not found] <Ft4B.3ML.3@gated-at.bofh.it>
     [not found] ` <FutO.5TB.29@gated-at.bofh.it>
2003-10-11 17:03   ` Ihar 'Philips' Filipau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031011044514.19799.qmail@web13005.mail.yahoo.com \
    --to=retu834@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®