The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] dmr note on BSD's sins
Date: Tue, 02 May 2017 09:11:52 -0700	[thread overview]
Message-ID: <a6533db70fc0fc45073e5de11cf9ba5311d1416b@webmail.yaccman.com> (raw)
In-Reply-To: <1189db4c-a1f5-6d03-45ed-81f1a2c51685@telegraphics.com.au>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

I recall a paper Dennis wrote (maybe more like a note) that was titled
     echo -c considered harmful
(I think it was -c).   It decried the tendency, now completely out
of control, for everybody and their dog to piddle on perfectly good
code just because it's "open". 

Let's face it, programming languages today are more like shells --
they rise or fall on the quality of their libraries, and the
expression of algorithms (or even simplicity or efficiency) are
secondary.  And operating systems seem to exist mainly to host window
systems that vie for how deeply and obscurely they can hide vital
options, and pride themselves that striking any key at any time, no
matter how inadvertent, will cause some unexpected and unwanted
action.

I'm reminded of a friend of mine who took a math course, and said that
the professor "proved theorems by induction on the number of lemmas".

And yes, I'm sounding like a grumpy old fart this morning...

Steve

----- Original Message -----
From: "Toby Thain" <toby@telegraphics.com.au>
To:<tuhs at minnie.tuhs.org>
Cc:
Sent:Mon, 1 May 2017 14:09:07 -0400
Subject:Re: [TUHS] dmr note on BSD's sins

 On 2017-05-01 1:25 PM, ron minnich wrote:
 > 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?

 Not what you're looking for, but in recent times we'd just say YAGNI
- 
 You Ain't Gonna Need It.

 --T

 >
 > ron


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170502/feaee61b/attachment.html>


  reply	other threads:[~2017-05-02 16:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 17:25 ron minnich
2017-05-01 18:09 ` Toby Thain
2017-05-02 16:11   ` Steve Johnson [this message]
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=a6533db70fc0fc45073e5de11cf9ba5311d1416b@webmail.yaccman.com \
    --to=scj@yaccman.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).