From: Michael Witten <mfwitten@gmail.com>
To: "Jordi Gutiérrez Hermoso" <jordigh@octave.org>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
Richard Stallman <rms@gnu.org>,
gcc Mailing List <gcc@gcc.gnu.org>,
emacs-devel@gnu.org
Subject: Re: clang and FSF's strategy
Date: Thu, 23 Jan 2014 10:03:58 +0000 [thread overview]
Message-ID: <CAMOZ1BuLknscdnti45kDJgnXw=GD0ft=ARbDoSj=POyoS710DA@mail.gmail.com> (raw)
In-Reply-To: <1390401184.29263.5.camel@Iris>
On Wed, Jan 22, 2014 at 2:33 PM, Jordi Gutiérrez Hermoso wrote:
> The fact that these non-free tools are not based on gcc are a
> testament to how proprietary software developers cannot plug into gcc,
> and how clang is fostering non-free software.
What does it matter whether clang fosters non-free software if clang *also*
fosters free software? Indeed, non-free software inspires a lot of free
software, anyway.
Apparently, gcc isn't fostering much of anything, except for a desire to
replace it with llvm/clang.
Where there is the least friction, there is the most freedom.
next prev parent reply other threads:[~2014-01-23 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 20:19 clang and FSF's strategy Eric S. Raymond
2014-01-22 0:07 ` David Kastrup
2014-01-25 15:26 ` David Kastrup
2014-01-22 0:50 ` Alexandre Oliva
2014-01-23 18:21 ` Joseph S. Myers
2014-01-22 1:31 ` Stefan Monnier
2014-01-22 1:31 ` Ian Lance Taylor
2014-01-22 4:02 ` Eric S. Raymond
2014-01-22 11:27 ` David Kastrup
2014-01-22 14:33 ` Jordi Gutiérrez Hermoso
2014-01-23 10:03 ` Michael Witten [this message]
2014-01-23 10:52 ` David Kastrup
2014-01-23 17:17 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 4:49 grischka
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='CAMOZ1BuLknscdnti45kDJgnXw=GD0ft=ARbDoSj=POyoS710DA@mail.gmail.com' \
--to=mfwitten@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=gcc@gcc.gnu.org \
--cc=jordigh@octave.org \
--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.