From: paul.winalski@gmail.com (Paul Winalski)
Subject: [TUHS] Happy birthday, computer mouse!
Date: Fri, 27 Apr 2018 14:23:25 -0400 [thread overview]
Message-ID: <CABH=_VSdpeSYBk5GE=+93D6wo8UqA1rwGZvvmpHRSHjCAszhUA@mail.gmail.com> (raw)
In-Reply-To: <777DD6D1-467D-4486-82E2-495AAE863F43@ronnatalie.com>
On 4/27/18, Ronald Natalie <ron at ronnatalie.com> wrote:
>
> PARC is well known for contributing things to the public that Xerox never
> quite got into a real product. I always loved going to meetings there just
> to see what they had come up with this time.
For a while Gordon Bell used to hand out the Xerox PARC Award to the
R&D project that simultaneously did the most to advance the state of
the art and contributed the least to DEC's bottom line.
-Paul W.
next prev parent reply other threads:[~2018-04-27 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 9:57 Dave Horsfall
2018-04-27 10:18 ` Hellwig Geisse
2018-04-27 10:58 ` William Corcoran
2018-04-27 11:13 ` Peter Jeremy
2018-04-27 12:13 ` Bakul Shah
2018-04-27 14:47 ` Ronald Natalie
2018-04-27 18:23 ` Paul Winalski [this message]
2018-04-27 12:48 ` Steffen Nurpmeso
2018-04-27 21:00 ` Cág
2018-04-27 23:06 ` Dave Horsfall
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='CABH=_VSdpeSYBk5GE=+93D6wo8UqA1rwGZvvmpHRSHjCAszhUA@mail.gmail.com' \
--to=paul.winalski@gmail.com \
/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).