The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "A. P. Garcia" <a.phillip.garcia@gmail.com>
To: Chris Hanson <cmhanson@eschatologist.net>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Isaacson v Unix
Date: Sat, 5 Jan 2019 21:18:40 -0500	[thread overview]
Message-ID: <CAFCBnZvJGU6ADx2KeJR_y3q1ODAd6waLSHq==ZjJXCXWbYD78g@mail.gmail.com> (raw)
In-Reply-To: <EA79006D-6494-43F2-A211-FCC8529D428B@eschatologist.net>

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

On Sat, Jan 5, 2019, 8:50 PM Chris Hanson <cmhanson@eschatologist.net wrote:

> On Jan 5, 2019, at 9:01 AM, A. P. Garcia <a.phillip.garcia@gmail.com>
> wrote:
>
> On Sat, Jan 5, 2019, 10:39 AM Larry McVoy <lm@mcvoy.com wrote:
>
>> +1.  RMS always talked big but the real work was done by other people.
>> GCC was Tiemann at Sun and then at Cygnus, groff was James Clark,
>> etc.  I think RMS hacked on emacs but not much else.
>>
>
> I'm going to refrain from either praising or disparaging the man. I think
> the book Hackers by Steven Levy does a good job of describing him and how
> the idea for the GNU project came about.
>
>
> Dan Weinreb, who was in charge of Symbolics at the time, strongly disputed
> the RMS (and “Hackers”) story of GNU’s inspiration from what Symbolics “did
> to” the AI Lab.
>
> By Weinreb’s account, Symbolics hired relatively few people away from the
> Lab, and  RMS wasn’t simply rewriting Symbolics’ enhancements (which were
> shared with the Lab, and Symbolics’ customers of course) for the MIT and
> LMI environments, he was actually caught copying their code directly.
>

A google search turned up a speech by rms that I hadnˋt previously seen, as
well as Weinrebˋs rebuttal:

https://www.gnu.org/gnu/rms-lisp.en.html

http://ergoemacs.org/misc/Daniel_Weinreb_rebuttal_to_rms.html

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

  reply	other threads:[~2019-01-06  2:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05  2:26 Doug McIlroy
2019-01-05  2:35 ` Ronald Natalie
2019-01-05 15:31   ` Larry McVoy
2019-01-05 17:01     ` A. P. Garcia
2019-01-05 20:27       ` Paul Winalski
2019-01-05 21:38         ` A. P. Garcia
2019-01-05 21:51           ` Rob Pike
2019-01-05 21:53             ` Rob Pike
2019-01-05 21:52           ` Larry McVoy
2019-01-06  1:50       ` Chris Hanson
2019-01-06  2:18         ` A. P. Garcia [this message]
2019-01-05 17:07     ` Donald ODona
2019-01-05 21:20       ` joe mcguckin
2019-01-06  1:43     ` Chris Hanson
2019-01-06  2:40       ` [TUHS] Emacs (was: Isaacson v Unix) Greg 'groggy' Lehey
2019-01-06  6:01         ` Donald ODona
2019-01-06  6:03           ` Larry McVoy
2019-01-06  6:26         ` Chris Hanson
2019-01-06  7:50         ` [TUHS] Emacs Lars Brinkhoff
2019-01-06 14:23           ` Andrew Luke Nesbit
2019-01-06 14:30             ` Lars Brinkhoff
2019-01-05  9:08 ` [TUHS] Isaacson v Unix William Corcoran
2019-01-05 12:09   ` Ed Carp
2019-01-05 14:15 ` Paul Winalski
2019-01-05 15:01   ` Ed Carp
2019-01-06  4:35 ` Bakul Shah
2019-01-06  4:52   ` Bakul Shah
2019-01-06  5:00   ` Toby Thain
2019-01-05  4:20 Noel Chiappa
2019-01-05 14:30 Noel Chiappa
2019-01-05 15:04 ` Ed Carp
2019-01-05 15:26   ` Warner Losh
2019-01-05 15:37     ` Ben Greenfield via TUHS
2019-01-05 21:34 Doug McIlroy
     [not found] <mailman.2.1546724053.30035.tuhs@minnie.tuhs.org>
2019-01-06  3:45 ` Paul McJones

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='CAFCBnZvJGU6ADx2KeJR_y3q1ODAd6waLSHq==ZjJXCXWbYD78g@mail.gmail.com' \
    --to=a.phillip.garcia@gmail.com \
    --cc=cmhanson@eschatologist.net \
    --cc=tuhs@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).