From: jss@ou.edu (Jeffrey S. Sharp)
Subject: [pups] Us vs. Museums
Date: Sun, 04 Mar 2001 09:43:54 -0600 (CST) [thread overview]
Message-ID: <983720634.3aa262babe633@email.ou.edu> (raw)
I don't know everyone's perspective on this issue, and it would be good to hear
some alternate viewpoints. Basically, I am against people giving classic
computers in working condition to museums. Instead, I believe that they should
donate or sell their machines to enthusiasts who will play with them and learn
things.
A while back, I ran across a person that had some hardware I wanted. He was
torn between selling it to me and giving it to a museum. I didn't have a lot
of money available to give him, and donation to a museum (a nonprofit) would
get him an impressive tax deduction. I did some research about what it takes
to start a nonprofit organization, but it looked too expensive (lawyers) and
time-consuming to be a viable option for me. I sent the following argument to
him:
> While I would love to establish a collection of these machines,
> I'm definitely not a 'collector' as the term has come to mean
> today; I'm not in it to get something rare, to make money, or
> to have some pretty decorations in my house. While it would
> certainly be nice to have a pretty system, my priority is to
> get something that I can learn with. I want to *run* these
> machines. I want to *explore* these machines. I want to *hack*
> on these machines, to see what unexpected things they can be
> coerced into doing. I want to get as close as I can to the
> *experience* of computing in these machines' era. If these
> machines go to a museum, they're just pretty art, and they will
> educate _no_one_. They will sit behind glass walls, no one
> ever will touch them again, and no one will ever turn them on or
> keep them in working order. They are effectively lost. That's
> little better then scrapping them, and you _KNOW_ how you feel
> about that!
What do you think about this?
(BTW, if anyone wants to use the quoted paragraph, they are free to)
--
Jeffrey S. Sharp
jss at ou.edu
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS/MU d-@ s-:+ a-- C+++(++++) UB+++$> P+ L+(++) E>
W++ N+(++) o? K? w++$ !O M(-) !V PS+++ PE Y+ PGP t+
5 X(+) R++ tv+ b+ DI++(+++) D+ G++ e> h--- r+++ y+++
------END GEEK CODE BLOCK------
next reply other threads:[~2001-03-04 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 15:43 Jeffrey S. Sharp [this message]
2001-03-04 23:27 ` [pups] " Merle K. Peirce
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=983720634.3aa262babe633@email.ou.edu \
--to=jss@ou.edu \
/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).