The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <>
To: Larry McVoy <>
Cc: TUHS main list <>
Subject: Re: [TUHS] Threads vs... not
Date: Thu, 5 Aug 2021 16:32:19 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

On Wed, Aug 4, 2021 at 6:51 PM Larry McVoy <> wrote:

> Sometimes threads make sense, there they did not.

Right. The problem is too often people have a hammer and make everything a
nail.   Or they have an electric screwdriver and then try to use if for
everything.  The trick is to teach good taste and when certain solutions
make more sense than others.   Allocating a thread for every page being
sent to disk, or needing 120 threads for a simple application -- somebody
missed the boat.

Funny, used to deliver nails in kegs.  Hit with a hammer - wood fastened.
Somebody develops a screw system.  A 'better fastener.' Indeed it does work
great for >>some jobs<< but not all.   Frankly that sucks for framing.
 What do you see at any real job site. Not screws but a pneumatic hammer
and nail cartridges?  Changed the deliver system from key and forcing
somebody to swing the hammer.

Lesson learned to *use the proper tool *or update the tool if the
>>technique<< is the right one.

Kids these days ... get off my lawn...


[-- Attachment #2: Type: text/html, Size: 2722 bytes --]

  reply	other threads:[~2021-08-05 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 21:48 Lawrence Stewart
2021-08-04 22:02 ` Larry McVoy
2021-08-04 22:41   ` John Cowan
2021-08-04 22:51     ` Larry McVoy
2021-08-05 20:32       ` Clem Cole [this message]
2021-08-06  0:55       ` Dan Cross
2021-08-04 22:13 ` Anthony Martin
2021-08-05 23:02 ` Bakul Shah
2021-08-06 14:19   ` Steffen Nurpmeso
2021-08-06 14:43     ` John Cowan
2021-08-06 15:12       ` Steffen Nurpmeso

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:

* 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).