9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matt H <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] code complexity
Date: Tue,  5 Feb 2002 14:47:57 +0000	[thread overview]
Message-ID: <20020205144757.517735c3.matt@proweb.co.uk> (raw)
In-Reply-To: <200202051424.GAA18255@ohio.river.org>

> And yet, it is still decidedly a minority view, even
> among programmers.  Why?
 
I reckon it's from not having to fit everything into 1k, 16k, 32k, 64k, 640k 

or 24 lines
or over 9600 baud

there won't be too many more Mels

http://tuxedo.org/~esr/jargon/html/The-Story-of-Mel.html

Matt


  reply	other threads:[~2002-02-05 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 14:24 Richard Uhtenwoldt
2002-02-05 14:47 ` Matt H [this message]
2002-02-05 16:34 Russ Cox
2002-02-05 16:39 ` Boyd Roberts
2002-02-05 16:42   ` Ronald G Minnich
2002-02-05 17:20     ` david presotto
2002-02-05 23:06       ` Steve Kilbane
2002-02-05 20:24 ` philw
2002-02-06  1:01   ` ozan s yigit
2002-02-05 22:28 ` Dan Cross
2002-02-05 16:41 Russ Cox
2002-02-06  0:10 [9fans] XP (was: code complexity) geoff
2002-02-06  0:29 ` [9fans] code complexity George Michaelson
2002-02-06 10:47   ` Boyd Roberts
2002-02-06 20:49     ` Andrew Simmons

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=20020205144757.517735c3.matt@proweb.co.uk \
    --to=matt@proweb.co.uk \
    --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).