The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Charles Forsyth on putting Unix on a diet.
Date: Sat, 28 Oct 2017 00:39:20 +0100	[thread overview]
Message-ID: <2FB588AE-7017-4DFE-AE6D-1FA3BB5C470F@tfeb.org> (raw)
In-Reply-To: <ae850e26da050f28a43ba0f3793c93dc@quintile.net>

> On 28 Oct 2017, at 00:15, Steve Simon <steve at quintile.net> wrote:
> 
> It was put to me that there is a big difference between
> complicated and complex.
> 
> Complexity may be necessary to deal with difficult problems.
> But the solution, built on the complex framework should never
> be complicated.

This is half-way (and perhaps more than that) to what the 'worse is better' paper would call 'the MIT approach'.  I think it's fairly obviously the right thing, and equally obviously almost never done.

--tim


  reply	other threads:[~2017-10-27 23:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 10:36 Noel Chiappa
2017-10-27 13:03 ` Clem Cole
2017-10-27 13:23   ` Steve Nickolas
2017-10-27 21:51     ` Andy Kosela
2017-10-27 23:04       ` Larry McVoy
2017-10-27 23:15         ` Steve Simon
2017-10-27 23:39           ` Tim Bradshaw [this message]
2017-10-28  2:00       ` Bakul Shah
2017-10-28  2:34         ` Lyndon Nerenberg
2017-10-28  2:42           ` Lyndon Nerenberg
2017-10-28  6:38           ` Bakul Shah
2017-10-27 21:43   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2017-10-28 13:11 Norman Wilson
2017-10-27 21:30 Norman Wilson
2017-10-27 22:49 ` Chris Torek
2017-10-26 14:57 Doug McIlroy
2017-10-26 22:07 ` George Michaelson
2017-10-25  2:51 Dan Cross
2017-10-25  3:14 ` Larry McVoy
2017-10-26 17:27 ` Larry McVoy
2017-10-26 22:12   ` George Michaelson
2017-10-27  3:49     ` Steve Nickolas
2017-10-27  6:55       ` arnold
2017-10-27  7:30   ` Derek Fawcus
2017-10-27  9:44     ` David Arnold

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=2FB588AE-7017-4DFE-AE6D-1FA3BB5C470F@tfeb.org \
    --to=tfb@tfeb.org \
    /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).