From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pjb@informatimago.com, Chong Yidong <cyd@gnu.org>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: clang/emacs/ecb/semantic
Date: Mon, 03 Dec 2012 10:14:19 -0800 [thread overview]
Message-ID: <50BCEBFB.1090004@dancol.org> (raw)
In-Reply-To: <838v9frpcq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
On 12/3/12 9:56 AM, Eli Zaretskii wrote:
>> From: Chong Yidong <cyd@gnu.org>
>> Cc: Daniel Colascione <dancol@dancol.org>, pjb@informatimago.com, rms@gnu.org, emacs-devel@gnu.org
>> Date: Tue, 04 Dec 2012 01:21:09 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>> More to the point, you seem to say that the line was drawn in the
>>> wrong place in this matter. But you never say why it was wrong, in
>>> practical terms
>>
>> The practical terms are in the subject of this thread, i.e. the fact
>> that there is no GPL'ed compiler which can provide the parse data needed
>> by a modern IDE.
>
> And there wasn't a GPL'ed text editor that supported bidirectional
> editing 2 years ago. So what? All it means that no one stepped
> forward and did that in a way that was acceptable. It certainly
> doesn't mean the FSF should fall for the first opportunity out there,
> just because there's no other solution.
There was no GPLed text editor supporting bidirectional editing
because the work hadn't been done. (Thanks again for doing that work.)
The gcc situation is different: multiple parties stepped forward to do
the work required to integrate gcc with other tools, and the gcc
developers refused to accept it. I don't think there is any technical
that would satisfy both the technical requirements of external tools
and the political requirements of the gcc developers.
Licensing is one thing, but a modular gcc, covered by the GPL, would
itself be just as free as today's gcc. (As would an Emacs with an FFI,
for that matter.) Technical restrictions are something else.
Reducing functionality can *never* serve the cause of software
freedom. Free programs should be as technically strong as possible,
even if that means they can talk to non-free programs. It's up to
developers to produce free software so good that users choose to use
free programs together, and crippling free software so that it can't
interoperate with *anything*, be it free or non-free, is a "see no
evil" approach that's not only a strategic blunder, but an affront to
users.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2012-12-03 18:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 16:32 clang/emacs/ecb/semantic Ramneek Handa
2012-11-29 19:59 ` clang/emacs/ecb/semantic Dmitry Gutov
2012-11-29 20:27 ` clang/emacs/ecb/semantic David Engster
2012-11-29 20:38 ` clang/emacs/ecb/semantic Óscar Fuentes
2012-11-29 20:49 ` clang/emacs/ecb/semantic David Engster
2012-11-30 2:52 ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30 6:34 ` clang/emacs/ecb/semantic Pascal J. Bourguignon
2012-11-30 15:15 ` clang/emacs/ecb/semantic David Engster
2012-11-30 15:25 ` clang/emacs/ecb/semantic ramneek
2012-12-01 4:44 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-04 17:04 ` clang/emacs/ecb/semantic David Engster
2012-11-30 20:11 ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30 21:02 ` clang/emacs/ecb/semantic Óscar Fuentes
2012-12-01 19:30 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-01 19:30 ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30 21:50 ` clang/emacs/ecb/semantic Pascal J. Bourguignon
2012-12-02 4:15 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-02 5:13 ` clang/emacs/ecb/semantic Daniel Colascione
2012-12-03 0:02 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 1:42 ` clang/emacs/ecb/semantic Daniel Colascione
2012-12-03 17:08 ` clang/emacs/ecb/semantic Eli Zaretskii
2012-12-03 17:21 ` clang/emacs/ecb/semantic Chong Yidong
2012-12-03 17:56 ` clang/emacs/ecb/semantic Eli Zaretskii
2012-12-03 18:14 ` Daniel Colascione [this message]
2012-12-03 18:50 ` clang/emacs/ecb/semantic Eli Zaretskii
2012-12-03 19:37 ` clang/emacs/ecb/semantic Stefan Monnier
2012-12-04 0:51 ` clang/emacs/ecb/semantic joakim
2012-12-04 2:17 ` clang/emacs/ecb/semantic Stefan Monnier
2012-12-04 1:04 ` clang/emacs/ecb/semantic joakim
2012-12-04 0:41 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 19:34 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-02 9:04 ` clang/emacs/ecb/semantic Stephen J. Turnbull
2012-12-02 13:48 ` clang/emacs/ecb/semantic Helmut Eller
2012-12-03 0:02 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 16:02 ` clang/emacs/ecb/semantic Burton Samograd
2012-12-04 0:40 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-04 14:05 ` clang/emacs/ecb/semantic Miguel Guedes
2012-12-05 11:49 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-05 17:21 ` clang/emacs/ecb/semantic Paul Eggert
2012-12-03 0:02 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-02 13:59 ` clang/emacs/ecb/semantic Pascal J. Bourguignon
2012-12-03 0:02 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 0:02 ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 0:02 ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30 6:46 ` clang/emacs/ecb/semantic Helmut Eller
2012-11-30 2:51 ` clang/emacs/ecb/semantic 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50BCEBFB.1090004@dancol.org \
--to=dancol@dancol.org \
--cc=cyd@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pjb@informatimago.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).