9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design issues in operating systems
Date: Mon,  3 Dec 2001 18:04:23 +0200	[thread overview]
Message-ID: <20011203180423.J788@cackle.proxima.alt.za> (raw)
In-Reply-To: <20011203160800.D526A1998A@mail.cse.psu.edu>; from anothy@cosym.net on Mon, Dec 03, 2001 at 11:07:49AM -0500

On Mon, Dec 03, 2001 at 11:07:49AM -0500, anothy@cosym.net wrote:
>
> why are people talking about design and evolution as though
> they're mutually exclusive?
>
To a degree, that's the case, though.  Design enforces rigidity and
wherever there's flexibility there's also room for error, which is
what design attempts to factor out.  Flexibility is where adaptation
occurs, with fatal mutations more the norm than the exception.

> a good design is one which is simple enough to comfortably
> allow for reasonable evolution. whereas i agree design _is_
> predictave, the results need not be static.
>
Simplicity in design (minimalism, in fact) is the ideal, in that its
rigidity is limited to essentials and, hopefully, does not apply to
the growth/evolution areas.  My opinion is that one should formalise
useful adaptations and absorb them into a design, which is the way I
think we humans operate at an intellectual level.

The difficulty is finding the motivation or vision to abandon baggage
whose function is exclusively to provide a familiar environment.
Remembering that in this forum I suggested not long ago that one
should not underestimate the importance of familiarity :-)

In this context, familiarity is just another evolutionary pressure
and, I must point out, evolution has no foresight, its purpose is to
increase the viability of an organism in the present, immediately
adjacent environment.

The mistake of assuming that evolution is progressive is evident even
in Linus Torvald's statement quoted earlier: the implication is that
an evolved Linux is somehow "better" that its predecessors.  It could
be agreed that it is better equipped for survival, but not necessarily
superior in some intellectual sense.

Materialists may well argue that that is all that counts, of course.

++L


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

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 16:07 anothy
2001-12-03 16:04 ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-05  8:49 Fco.J.Ballesteros
2001-12-04 17:27 erik quanstrom
2001-12-04 10:36 forsyth
2001-12-03 22:50 jmk
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 21:31 rob pike
2001-12-03 16:27 presotto
2001-12-03 15:45 bwc
2001-12-03 14:49 bwc
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
2001-12-05  9:56   ` Douglas A. Gwyn

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=20011203180423.J788@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).