9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John S. Dyson" <dyson@iquest.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design issues in operating systems
Date: Mon,  3 Dec 2001 16:55:52 +0000	[thread overview]
Message-ID: <c66cd78b.0112030847.194c589d@posting.google.com> (raw)
In-Reply-To: <48effcda.0112022010.d4a2c9f@posting.google.com>

north_ <northern_snow78@yahoo.com> wrote in message news:<48effcda.0112022010.d4a2c9f@posting.google.com>...
> Ok, normally I do not take the time to write responses regarding
> issues like these. However, I believe Linus is a bit misguided
> and I would like to quickly postulate why. This isn't just a
> Linux problem. Its a lifestyle problem. You will see why I
> believe so in just one second or so ;)
> > --- bla bla bla snip ---
> > If you want to see a system that was more thoroughly _designed_, you
> > should probably point not to Dennis and Ken, but to systems like L4 and
> > Plan-9, and people like Jochen Liedtk and Rob Pike.
> >
> > And notice how they aren't all that popular or well known? "Design" is
> > like a religion - too much of it makes you inflexibly and unpopular.
> *G*.
> Design is in actuality nothing more than a personal concept. Design
> itself is a facade.
>

Well, most of the Linux (and *BSD) design wasn't done by those
who are working on it today.  Linux was a copy of a previous
design work done by someone else.

There might be some superior re-implementation in Linux or *BSD,
but claiming that Linux was designed by those who code it would
strongly imply that the concepts were also authored.  Without
the template provided by previous UNIX implementations, there would
not have been a template for Linux or *BSD.

There is some common source heritage between BSD and SVR4, but
the seed design certainly came from a couple of Bell Labs guys.

In an informal sense, the Linux developers might claim that they
designed the code.  However, making the proclaimation that Linux
was designed starting with the first line of code written for
it would be rather overstated.  Linux was essentially DESIGNED
(but not IMPLEMENTED) before the first line of code was written.

John


  reply	other threads:[~2001-12-03 16:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02 17:05 Andrey A Mirtchovski
2001-12-03 10:09 ` josh d
2001-12-03 15:24   ` Ronald G Minnich
2001-12-03 15:08     ` Lucio De Re
2001-12-03 15:48     ` andrey
2001-12-03 18:03   ` Ozan Yigit
2001-12-03 20:51     ` Mike Haertel
2001-12-03 10:10 ` north_
2001-12-03 16:55   ` John S. Dyson [this message]
2001-12-05  9:56   ` Douglas A. Gwyn
2001-12-03 14:49 bwc
2001-12-03 15:45 bwc
2001-12-03 16:07 anothy
2001-12-03 16:04 ` Lucio De Re
2001-12-03 16:27 presotto
2001-12-03 21:31 rob pike
2001-12-03 21:34 rob pike
2001-12-03 22:01 ` Alexander Viro
2001-12-04 19:05   ` Dan Cross
2001-12-04 21:59     ` Alexander Viro
2001-12-07  9:36       ` Barry
2001-12-03 22:50 jmk
2001-12-04 10:36 forsyth
2001-12-04 17:27 erik quanstrom
2001-12-05  8:49 Fco.J.Ballesteros

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=c66cd78b.0112030847.194c589d@posting.google.com \
    --to=dyson@iquest.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).