all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: jean.christophe.helary@gmail.com, jostein@kjonigsen.net,
	emacs-devel@gnu.org
Subject: Re: Licence of ts-comint
Date: Tue, 22 Aug 2017 12:12:15 -0400	[thread overview]
Message-ID: <E1dkBmp-0007z4-0y@fencepost.gnu.org> (raw)
In-Reply-To: <m2y3qcu0x6.fsf@newartisans.com> (message from John Wiegley on Mon, 21 Aug 2017 13:21:41 -0700)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Not necessarily. nVidia has enough money they could write their own backends
  > from scratch,

The GPL does not allow linking GCC front ends with nonfree backends.
They would have had to write an entire compiler.

		  which would mean users losing out on all the research that's
  > gone into LLVM, any chance of compatibility with standard tools, etc.

These are side issues when our freedom is at stake.

  > No company with sufficient resources is forced to participate in free
  > software,

nVidia could, in principle, have written a compiler from scratch.  In
practice, that is a big job and success is not guaranteed.  nVidia's
compiler might not have worked as well.  It might not have worked well
at all.  It might have been too expensive to finish.  nVidia might
have given up, at the outset or after a couple of years of work.

The GPL has induced many basically uncooperative companies and
organizations to contribute their code to the free world
so that they could use GPL-covered code.

They are pretty strongly pressured, and that's usualy good enough.

If only the developers of LLVM had not given nVidia a way to bypass
our pressure, I think we would have a free compiler for a known
instruction set.

  > Without free software, we would simply
  > descend into further fragmentation, lack of interoperability, and no chance at
  > all to benefit from the work of others.

When that work is nonfree software, the invitation to use it is hardly a
benefit.  It's a trap.

Of course, there are various sorts of secondary benefits and secondary
problems.  Everything that happens causes secondary benefits and
secondary problems.  Those are side issues.


-- 
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.




  reply	other threads:[~2017-08-22 16:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C7FBB42B-2311-44F5-B940-22426AC1B2B7@gmail.com>
2017-08-13 10:58 ` Licence of ts-comint Jostein Kjønigsen
2017-08-13 12:15   ` Jean-Christophe Helary
2017-08-14  1:51     ` Richard Stallman
2017-08-13 18:16   ` Paul Eggert
2017-08-13 22:01   ` Stefan Monnier
2017-08-13 23:35     ` John Wiegley
2017-08-14  2:35       ` Eli Zaretskii
2017-08-14 20:48       ` Richard Stallman
2017-08-14 20:54         ` John Wiegley
2017-08-15  2:27           ` Eli Zaretskii
2017-08-21 19:03   ` Richard Stallman
2017-08-21 20:21     ` John Wiegley
2017-08-22 16:12       ` Richard Stallman [this message]
2017-08-22 17:33         ` John Wiegley
2017-08-23  3:51           ` [OFFTOPIC] " Stefan Monnier
2017-08-23  4:36             ` Radon Rosborough
2017-08-23  5:36               ` Paul Eggert
2017-08-23  5:56                 ` John Wiegley
2017-08-23 22:50                 ` Richard Stallman
2017-08-23 11:32               ` Stefan Monnier
2017-08-23 22:50             ` Richard Stallman
2017-08-24 10:40               ` Stefan Monnier
2017-08-23 14:18           ` Richard Stallman
2017-08-22 17:33         ` John Yates
2017-08-22 17:54           ` Paul Eggert
2017-08-22 20:16             ` John Yates
2017-08-23  0:30               ` Paul Eggert
2017-08-23 22:48               ` Richard Stallman
2017-08-22 16:12       ` Richard Stallman
2017-08-22 16:12       ` Richard Stallman

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=E1dkBmp-0007z4-0y@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    --cc=jostein@kjonigsen.net \
    --cc=jwiegley@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.