From: Paul Schlie <schlie@comcast.net>
To: <gdb@sources.redhat.com>
Subject: Re: GDB is the GNU project's native debugger
Date: Tue, 16 Nov 2004 19:51:00 -0000 [thread overview]
Message-ID: <BDBFBF91.7F9E%schlie@comcast.net> (raw)
> Ian Lance Taylor wrote:
> For what it's worth, I believe that is to some degree a
> misunderstanding. The goal of the FSF is a completely free system
> (this goal has been achieved). This free system is intended to be
> superior both technically and philosophically, and thus encourage
> people to switch to it.
>
> Running free tools on non-free systems is interesting only to the
> extent that it helps lead to a fully free system. This happens
> because it encourages a broader range of people to put resources into
> improving the free tools, and thus improving the free system.
> However, running free tools on non-free systems is counterproductive
> to the extent that they make the non-free systems more usable, and
> thus delay the adoption of completely free systems.
>
> Using the free tools as advertisements of the effectiveness of the GNU
> project is not actually a goal of the FSF, contrary to what you
> suggest.
As a not so minor nit, the notion of "FREE" needs to clarified:
- "FREE" from GNU's perspective has always predominantly referred to the
intellectual properly content being "FREE" of proprietary encumbrances.
- there's no such thing as "FREE" from a financial/resource point of view,
everything consumes resources, and gets paid for one way or another; GNU's
project has been financed/resourced by both individuals and corporations
simply because it's either perceived as either the right thing to do, or
(more often than not) simply perceived as being less expensive than
alternative solutions.
- arguably, adopting any bias which inhibits the applicability of GNU's
tools, actually encourages/requires the development of likely proprietary
alternatives in contradiction of GNU's goals, and indirectly reducing
opportunity to fund continued advancements, (which seems quite counter
productive overall).
next reply other threads:[~2004-11-16 19:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 19:51 Paul Schlie [this message]
2004-11-16 21:11 ` Paul Breed
2004-11-16 23:58 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 19:30 Paul Schlie
2004-11-16 17:14 Andrew Cagney
2004-11-16 17:26 ` Paul Breed
2004-11-16 17:35 ` Kris Warkentin
2004-11-16 20:09 ` Mark Kettenis
2004-11-16 17:50 ` Ian Lance Taylor
2004-11-16 21:48 ` Eli Zaretskii
2004-11-17 1:24 ` Andrew Cagney
2004-11-17 1:53 ` Ian Lance Taylor
2004-11-17 22:59 ` Andrew Cagney
2004-11-19 5:05 ` Ian Lance Taylor
2004-11-19 7:19 ` Kip Macy
2004-11-30 16:26 ` Andrew Cagney
2004-12-07 14:46 ` Ian Lance Taylor
2004-11-16 18:11 ` Dave Korn
2004-11-16 18:33 ` Ian Lance Taylor
2004-11-16 18:43 ` Dave Korn
2004-11-16 18:47 ` Ian Lance Taylor
2004-11-16 19:59 ` Mark Kettenis
2004-11-17 0:31 ` Steven Johnson
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=BDBFBF91.7F9E%schlie@comcast.net \
--to=schlie@comcast.net \
--cc=gdb@sources.redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox