From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Maybe it is april fool's after all ...
Date: Sat, 21 Jan 2006 08:09:31 -0500 [thread overview]
Message-ID: <7895ab53013a9da5835d453e28bd4ba1@coraid.com> (raw)
In-Reply-To: <175220925b5b1b6ea06e408fa9a51c2c@plan9.bell-labs.com>
And a sufficient quantity of bad source is the same, or worse, than
no source at all.
> On Fri Jan 20 23:28:05 EST 2006, quanstro@quanstro.net wrote:
>> just because you can't see the source, doesn't make it any better.
>> ...
>> - erik
>> ...
>
> the original point was that it doesn't matter whether you can
> see the source or not, the effect is the same - failure to deal
> with complexity results in an inability to simply compile a
> working programme on new hardware running the same O/S and have
> it work. instead, hacks are done and baggage is carried around
> to keep the old binary working.
>
> --jim
next prev parent reply other threads:[~2006-01-21 13:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 17:54 Ronald G Minnich
2006-01-19 20:43 ` Charles Forsyth
2006-01-19 22:28 ` Bruce Ellis
2006-01-20 11:58 ` Devon H. O'Dell
2006-01-20 16:08 ` jmk
2006-01-20 16:13 ` andrey mirtchovski
2006-01-20 22:19 ` Paweł Lasek
2006-01-21 4:01 ` jmk
2006-01-21 4:06 ` Bruce Ellis
2006-01-21 4:26 ` erik quanstrom
2006-01-21 5:09 ` jmk
2006-01-21 6:20 ` uriel
2006-01-21 8:36 ` Skip Tavakkolian
2006-01-21 7:42 ` Bruce Ellis
2006-01-21 13:09 ` Brantley Coile [this message]
2006-01-21 16:37 ` Ronald G. Minnich
2006-01-21 18:49 ` Bruce Ellis
2006-01-21 19:43 ` David Leimbach
2006-01-21 21:13 ` Skip Tavakkolian
2006-01-21 13:11 ` Brantley Coile
2006-01-20 17:33 ` David Leimbach
2006-01-20 17:36 ` Ronald G Minnich
2006-01-20 17:53 ` jmk
2006-01-20 18:10 ` Dave Lukes
2006-01-20 18:38 ` Lyndon Nerenberg
2006-01-21 19:29 ` Marina Brown
2006-01-20 20:14 ` Ronald G Minnich
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=7895ab53013a9da5835d453e28bd4ba1@coraid.com \
--to=brantley@coraid.com \
--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).