From: Aleksej Saushev <asau@inbox.ru>
To: linux-kernel@vger.kernel.org
Cc: netbsd-users@netbsd.org, ubuntu-users@lists.ubuntu.com,
fedora-list@redhat.com, freebsd-questions@freebsd.org
Subject: Re: GPL version 4
Date: Sun, 20 Jul 2008 12:34:17 +0400 [thread overview]
Message-ID: <87fxq59com.fsf@inbox.ru> (raw)
In-Reply-To: E1KKQd9-000114-IV@fencepost.gnu.org
Richard M Stallman <rms@gnu.org> writes:
> Freedom means having control of your own life. Using a proprietary
> program means giving the developer power over you. "More choice" in
> surrendering your freedom is not more freedom, and it does not make a
> better world.
"Breathing the air means giving anyone else power over you."
Even with proprietary programs you still have the control of
your life: noone forces you to use this or that program.
> It will just result in him producing a poorer, more expensive, less
> compatible product -- or none at all.
>
> Ideally, it will be none at all. A proprietary program is a negative
> contribution to society.
Oh, really. Programs are dearer to your heart than people.
What you say sounds luddist: it is better to force everyone to
perform routine tasks manually instead of saving time by minor
investment in development of tools.
> One less proprietary program means one less
> job of replacement on our list, and it could leave the field open for
> a free program to succeed.
You speculate on what it could or could not, yet many people
prefer to look at what is and what is not.
> Just think how much better off we would be
> if Microsoft Windows had never been developed.
How? How exactly? I don't believe you, show me facts.
> But suppose he does it anyway, without using our code. That could be
> just the handicap that enables a competing free program to be superior
> in convenience, just as it always is in ethics.
Put ethics aside, it is subjective and differs from place to place.
In which way your "free" "replacement" is more convenient than Adobe Photoshop?
How do you explain simple fact, that photographers prefer the latter,
even when they tried your so-called "free" so-called "replacement".
next prev parent reply other threads:[~2008-07-20 8:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aQmTc-5A5-3@gated-at.bofh.it>
2008-07-18 19:42 ` GPL version 4 Bodo Eggert
2008-07-19 0:47 ` David Schwartz
2008-07-19 3:05 ` Eric Furman
[not found] ` <E1KKQd9-000114-IV@fencepost.gnu.org>
2008-07-20 8:34 ` Aleksej Saushev [this message]
2008-07-20 12:21 ` Charles L. Nelson
2008-07-20 15:15 ` Kasper Sandberg
2008-07-17 8:31 Julian H. Stacey
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 21:31 Morton Harrow
2008-07-16 21:41 ` Valdis.Kletnieks
2008-07-16 22:23 ` Matthias Kilian
2008-12-14 21:12 ` Mark Kirkwood
2008-12-15 0:27 ` Marco Peereboom
2008-12-15 1:31 ` Mark Kirkwood
2008-12-15 1:44 ` bofh
2008-12-15 1:43 ` Damien Miller
[not found] ` <E1LCDed-0001OK-UC@fencepost.gnu.org>
2008-12-15 20:51 ` Chad Perrin
2008-07-16 22:06 ` David Collier-Brown
2008-07-17 21:17 ` linux-os (Dick Johnson)
2008-07-17 21:24 ` Valdis.Kletnieks
2008-07-16 22:08 ` Al Viro
2008-07-17 2:12 ` Kasper Sandberg
2008-07-17 11:21 ` Alexandre Oliva
2008-07-16 18:09 Morton Harrow
2008-07-16 18:43 ` Adrian Bunk
2008-07-16 19:14 ` Valdis.Kletnieks
2008-07-16 21:48 ` Jan Engelhardt
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=87fxq59com.fsf@inbox.ru \
--to=asau@inbox.ru \
--cc=fedora-list@redhat.com \
--cc=freebsd-questions@freebsd.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netbsd-users@netbsd.org \
--cc=ubuntu-users@lists.ubuntu.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 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.