From: Lars Brinkhoff <lars@nocrew.org>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] [tuhs] Computer history preservation
Date: Tue, 17 Sep 2019 05:21:06 +0000 [thread overview]
Message-ID: <7w7e67mrb1.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CMM.0.95.0.1568670516.beebe@gamma.math.utah.edu> (Nelson H. F. Beebe's message of "Mon, 16 Sep 2019 15:48:36 -0600")
"Nelson H. F. Beebe" <beebe@math.utah.edu> writes:
> I came across an article today about another major industry that has
> been exceedingly careless about preserving its history
It's an extenssion of the hype cycle. It starts like this:
1. Technology Trigger
2. Peak of Inflated Expectations
3. Trough of Disillusionment
4. Slope of Enlightenment
5. Plateau of Productivity
What is usually not pictured is the rest of the curve:
6. Dip of Sunset Technology.
7. Valley of Obsolete Stuff.
8. Throwing Away of Old Junk.
9. Resurge of Nostalgia.
10. Frantic Search on Ebay.
11. The Even Higher Peak of Collector's Holy Grail.
next prev parent reply other threads:[~2019-09-17 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 21:48 Nelson H. F. Beebe
2019-09-16 22:24 ` Gregg Levine
2019-09-16 23:44 ` Dave Horsfall
2019-09-17 0:28 ` Peter Jeremy
2019-09-17 7:46 ` Steve Nickolas
2019-09-17 5:21 ` Lars Brinkhoff [this message]
2019-09-17 15:33 ` Clem Cole
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=7w7e67mrb1.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=beebe@math.utah.edu \
--cc=tuhs@minnie.tuhs.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).