all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: rms@gnu.org
Cc: pmr@pajato.com, emacs-devel@gnu.org
Subject: Re: Emacs Webapp/Plugin
Date: Sun, 05 Aug 2012 09:31:31 +0900	[thread overview]
Message-ID: <87d3365gd8.fsf@catnip.gol.com> (raw)
In-Reply-To: <E1SxoKr-00013j-Pp@fencepost.gnu.org> (Richard Stallman's message of "Sat, 04 Aug 2012 20:04:45 -0400")

Richard Stallman <rms@gnu.org> writes:
> Chromium is a free browser.
> Chrome is a nonfree browser.

Right.

> Because we don't have the full source code of Google Chrome,
> we can't change it and we can't even tell what it does.
> The fact that parts of it are the same as another free program
> doesn't alter the problems.

Indeed, but that seems irrelevant to the point I'm trying to make.

>     My understanding was that although binary distributed by google wasn't
>     free, because it includes various bells and whistles implemented with
>     non-free libraries (e.g. video decoding ...?), the guts of the browser
>     _is_ actually free software,
>
> A combination of free code and nonfree code is nonfree.
> The free parts don't make the nonfree parts ok.

Nobody is saying they do.

What I'm trying to say is:

If chromium and chrome have the same app/plugin interface, then making
Emacs (or anything else) use that interface is targeting an interface
shared by _both_ free and non-free systems.

In that case, objections that "we shouldn't add this support because
it supports a non-free system" are not correct -- doing so would
support (completely) free systems as well, and that seems to make the
case for adding such support much stronger.

-miles

-- 
Inhumanity, n. One of the signal and characteristic qualities of humanity.



  reply	other threads:[~2012-08-05  0:31 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 16:47 Emacs Webapp/Plugin Paul Michael Reilly
2012-07-27 18:13 ` joakim
2012-07-27 23:56 ` Jeremiah Dodds
2012-07-28  2:56   ` Paul Michael Reilly
2012-07-28 21:26     ` William Gardella
2012-07-29 10:53       ` Paul Michael Reilly
2012-07-29 15:21         ` Bastien
2012-07-29 16:14         ` William Gardella
2013-10-04 10:03         ` Alex Bennée
2013-10-04 15:39           ` Paul Michael Reilly
2013-10-05 16:48             ` Richard Stallman
2013-10-06 18:59               ` Paul Michael Reilly
2013-10-07 13:36                 ` Richard Stallman
2012-07-28 13:58 ` Richard Stallman
2012-07-29  0:54   ` Miles Bader
2012-07-29 11:18     ` Paul Michael Reilly
2012-08-05 17:06     ` Richard Stallman
2012-08-08  5:19       ` William Gardella
2012-07-29 11:11   ` Paul Michael Reilly
2012-07-30  1:47     ` Richard Stallman
2012-07-30  2:34       ` Stephen J. Turnbull
2012-07-30  8:30         ` joakim
2012-07-31 22:32           ` Richard Stallman
2012-07-31 22:49             ` chad
2012-08-01  9:20               ` joakim
2012-08-01 22:42                 ` Richard Stallman
2012-08-02  7:41                   ` joakim
2012-08-02 23:38                     ` Richard Stallman
2012-08-03 19:09                       ` joakim
2012-08-04  5:43                         ` Richard Stallman
2012-08-02 23:38                     ` Richard Stallman
2012-08-03 19:27                       ` joakim
2012-08-04  5:43                         ` Richard Stallman
2012-08-04  8:13                           ` joakim
2012-08-04  2:43                       ` Jason Rumney
2012-08-05  0:04                         ` Richard Stallman
2012-07-31 22:32         ` Richard Stallman
2012-08-04 10:06       ` Miles Bader
2012-08-04 13:01         ` Lennart Borgman
2012-08-04 15:38           ` Nix
2012-08-05  0:04         ` Richard Stallman
2012-08-05  0:31           ` Miles Bader [this message]
2012-08-05 21:01             ` 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=87d3365gd8.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.com \
    --cc=rms@gnu.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.
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.