From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] simple, sufficient
Date: Tue, 8 Jul 2003 00:23:10 +0100 [thread overview]
Message-ID: <f437c03990794bda4bce4a4061e18dd7@vitanuova.com> (raw)
In-Reply-To: <008e01c344ce$b04576c0$d2944251@insultant.net>
> > sufficient for what?
>
> sufficient to do the job. everything is a trade-off ...
there are many different jobs...
some might even require >4GB unit transfer sizes to accomplish
the job efficiently enough.
for another, maybe 9p2000's extra 8 byte overhead on a Tread compared
to old 9p might make a crucial difference.
"simple and sufficient" is a platitude: i don't think anyone really
wants to introduce complexity for its own sake, and what's the point
in implementing something if it's not sufficient for the task you want
to solve?
what i think we're really after is... simple and *insufficient*; :-)
choose the things you *won't* be able to do (e.g. read >4GB in a
chunk, associate arbitrary metadata on a file) in order to gain
simplicity overall.
isn't this the reason for plan 9's beauty, and conversely perhaps, one
reason for its lack of popularity?
trade-offs (particularly trade-offs involving the sacrifice of some
potential feature in return for ill-defined simplicity) are hard.
many people are unwilling to make them; hence endlessly increasing
bloat.
next prev parent reply other threads:[~2003-07-07 23:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 18:04 [9fans] Rstat needs three size fields? Sam
2003-06-30 19:08 ` ron minnich
2003-06-30 19:15 ` boyd, rounin
2003-07-04 3:18 ` Russ Cox
2003-07-04 15:04 ` Sam
2003-07-04 17:13 ` rob pike, esq.
2003-07-07 8:33 ` Douglas A. Gwyn
2003-07-07 9:03 ` Geoff Collyer
2003-07-07 15:10 ` Douglas A. Gwyn
2003-07-08 0:49 ` ron minnich
2003-07-07 15:50 ` rob pike, esq.
2003-07-07 20:38 ` boyd, rounin
2003-07-07 21:18 ` rog
2003-07-07 21:28 ` boyd, rounin
2003-07-07 23:23 ` rog [this message]
2003-07-07 20:54 ` Geoff Collyer
2003-07-09 2:07 ` William Josephson
2003-07-07 15:48 ` rob pike, esq.
2003-07-07 15:58 ` Jack Johnson
2003-07-08 8:32 ` Douglas A. Gwyn
2003-07-08 10:30 ` boyd, rounin
2003-07-08 11:09 ` matt
2003-07-08 11:36 ` Dan Cross
2003-07-08 12:12 ` boyd, rounin
2003-07-08 14:14 ` ron minnich
2003-07-08 17:42 ` chris
2003-07-08 20:19 ` matt
2003-07-08 20:41 ` boyd, rounin
2003-07-09 14:58 ` rog
2003-07-09 19:42 ` boyd, rounin
2003-07-10 12:30 ` rog
2003-07-08 22:09 ` ron minnich
2003-07-08 22:19 ` Dan Cross
2003-07-09 1:27 ` ron 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=f437c03990794bda4bce4a4061e18dd7@vitanuova.com \
--to=rog@vitanuova.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).