The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Steinhart <jon@fourwinds.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Isaacson v Unix [really RMS bashing]
Date: Sun, 06 Jan 2019 15:41:33 -0800	[thread overview]
Message-ID: <201901062341.x06NfXe2021557@darkstar.fourwinds.com> (raw)

Been wanting to wade into this for a few days but needed to think about how.

I think that we're all aware that RMS has atrocious personal habits.  But I
don't think that this mailing list is the place to discuss them unless it's
somehow in the context of UNIX.

Many seem to excuse RMS's revisionist view of the history of technology on
the grounds that RMS claims that his memory isn't very good.  I think that
if he knows that he doesn't remember things then he should refrain from
talking about them as if he does.

As others have said, I don't conflate coding prowess with the ability to
design.  I've had many an argument with John Gilmore (one of the people
who doesn't mind footing the cleaning and repair bill after allowing RMS
to stay at his place) where he begins with "When I wrote GNU tar..."  I've
always responded by saying that writing tar is no big deal; the specification
was the hard part.

One place where I completely disagree with RMS that I think is in context
for this list is his claim that Linux should be called GNU/Linux.  I've
written tons of software in my life, and I don't preface the name of each
one with the parts list.

Even if one believed that such an attribution scheme made sense, I would
claim that it should be called internet/Linux.  I would argue that Linux
would not have happened without the internet making it possible for folks
around the world to participate.  And I think that there's a good chance
that the tools would have been created anyway.

Of course, I acknowledge that the GNU tools have been ported to Linux.
Big deal.  I haven't seen RMS arguing for GNU/Windows now that Microsoft
has seen the light.

Like many of you, Linux is not where I first started using GNU tools; I
started using them on my Sun machines after Sun started charging extra
for the compiler and included a licensing system that was broken and often
interfered with getting work done.

Jon

             reply	other threads:[~2019-01-07  0:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 23:41 Jon Steinhart [this message]
2019-01-07  1:29 ` A. P. Garcia
2019-01-07  1:59   ` Steve Nickolas
2019-01-07  2:39     ` Warner Losh
2019-01-07  2:59       ` A. P. Garcia
2019-01-07  3:32         ` Warner Losh
2019-01-07  5:05         ` Toby Thain
2019-01-07  5:36         ` Andy Kosela
2019-01-07  1:38 ` Toby Thain
2019-01-07  2:11   ` Larry McVoy
2019-01-07  2:31     ` A. P. Garcia
2019-01-07  0:49 Larry McVoy

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=201901062341.x06NfXe2021557@darkstar.fourwinds.com \
    --to=jon@fourwinds.com \
    --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).