From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] dmr note on BSD's sins
Date: Mon, 01 May 2017 17:25:33 +0000 [thread overview]
Message-ID: <CAP6exYK-iikmM1p4f-bNHh0_HSCwPGPCusp1f1S45vhEYmZbXg@mail.gmail.com> (raw)
OK, I recall a note dmr wrote probably in the late 70s/early 80s when folks
at UCB had (iirc) extended the symbol name size in C programs to
essentially unlimited. This followed on (iirc) file names going beyond 14
characters.
The rough outline was that dmr was calling out the revisions for being too
general, and the phrase "BSD sins" sticks in my head (sins as a verb).
I'm reminded of this by something that happened with some interns recently,
as they wanted to make something immensely complex to cover a case that
basically never happened. I was trying to point out that you can go
overboard on that sort of thing, and it would have been nice to have such a
quote handy -- anyone else remember it?
ron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170501/836c2a70/attachment.html>
next reply other threads:[~2017-05-01 17:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 17:25 ron minnich [this message]
2017-05-01 18:09 ` Toby Thain
2017-05-02 16:11 ` Steve Johnson
2017-05-02 16:39 ` Erik E. Fair
2017-05-02 16:43 ` ron minnich
2017-05-02 20:28 ` Diomidis Spinellis
[not found] ` <CAM4FNStH7KH6+ab0o_fYKfzutvPQ__0w0Zq5_6hk4AFP=+aSAw@mail.gmail.com>
2017-05-02 20:34 ` Daniel Camolês
2017-05-02 20:34 ` Steve Johnson
2017-05-02 21:22 ` Andy Kosela
2017-05-03 0:52 Doug McIlroy
2017-05-03 0:59 ` Dave Horsfall
2017-05-03 12:54 ` Dan Cross
2017-05-03 13:09 ` Arthur Krewat
2017-05-03 13:46 ` Michael Kjörling
2017-05-03 14:57 ` Clem Cole
2017-05-03 15:34 ` arnold
2017-05-03 15:44 ` Clem Cole
2017-05-03 13:41 Nemo
2017-05-03 22:18 ` Dave Horsfall
2017-05-04 14:59 ` Tim Bradshaw
2017-05-04 23:14 ` Larry McVoy
2017-05-05 14:01 ` Random832
2017-05-05 18:56 ` A. P. Garcia
2017-05-05 17:33 ` Tim Bradshaw
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=CAP6exYK-iikmM1p4f-bNHh0_HSCwPGPCusp1f1S45vhEYmZbXg@mail.gmail.com \
--to=rminnich@gmail.com \
/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).