From: Warner Losh <firstname.lastname@example.org>
To: josh <email@example.com>
Cc: steve jenkin <firstname.lastname@example.org>, TUHS <email@example.com>
Subject: [TUHS] Re: Clem's Law.
Date: Sun, 26 Jun 2022 22:51:09 -0600 [thread overview]
Message-ID: <CANCZdfr2_FdCNiiT8PrP5gvbnBFjE_-fYv=6848SQZo8J9pH=A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On Sun, Jun 26, 2022, 10:39 PM josh <firstname.lastname@example.org> wrote:
> > Clem Cole <email@example.com> wrote:
> > My own take on this is what I call "Cole's Law" Simple economics
> > always beats sophisticated architecture.
> Cole's Law is a bit of a better name than Clem's Law :P. Clem has
> invoked his law on this mailing list in various contexts, check out
> the archives.
I thought Cole's Law was thinly sliced cabbage. .
> On Sun, Jun 26, 2022 at 11:58 PM steve jenkin <firstname.lastname@example.org>
>> I thought this comment was very good.
>> I went looking for “Clem’s Law” (presume Clem Cole) and struck out.
>> Any hints anyone can suggest or history on the comment?
>> steve j
>> Larry McVoy wrote Fri Sep 17 10:44:25 AEST 2021
>> Plan 9 is very cool but I am channeling my inner Clem,
>> Plan 9 didn't meet Clem's law.
>> It was never compelling enough to make the masses love it.
>> Linux was good enough.
>> Steve Jenkin, IT Systems and Design
>> 0412 786 915 (+61 412 786 915)
>> PO Box 38, Kippax ACT 2615, AUSTRALIA
>> mailto:email@example.com http://members.tip.net.au/~sjenkin
[-- Attachment #2: Type: text/html, Size: 2768 bytes --]
next prev parent reply other threads:[~2022-06-27 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 3:58 [TUHS] " steve jenkin
2022-06-27 4:37 ` [TUHS] " josh
2022-06-27 4:51 ` Warner Losh [this message]
2022-06-27 7:14 ` Steve Jenkin
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).