From: "David Schwartz" <davids@webmaster.com>
To: <7eggert@gmx.de>, "Morton Harrow" <mharrow@linuxmail.org>,
"Kasper Sandberg" <lkml@metanurb.dk>,
"Miod Vallat" <miod@online.fr>, <licensing@fsf.org>,
<linux-kernel@vger.kernel.org>, <rms@gnu.org>,
<claire.newman@canonical.com>, <announce@fsfeurope.org>,
<misc@openbsd.org>, <ubuntu-users@lists.ubuntu.com>,
<fedora-list@redhat.com>, <netbsd-users@netbsd.org>,
<freebsd-questions@freebsd.org>
Subject: RE: GPL version 4
Date: Fri, 18 Jul 2008 17:47:46 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAEJDOEAC.davids@webmaster.com> (raw)
In-Reply-To: <E1KJvqk-0001Nh-QR@be1.7eggert.dyndns.org>
> Would you grant me the freedom to give away your commercial
> product for free
> or to incorporate it in my commercial product? Probably not. You'd instead
> grant me less freedom. The GPL protects me from this.
Except it doesn't. With or without the GPL, if he still makes his commercial
product, you will still be unable to give it away or incorporate it in your
commercial product. If he doesn't make it, that's just less choice for
everyone.
It may be a poorer product. It may cost him more to develop it. It may wind
up not existing. But in no case will will you wind up with the freedom to
give away his commercial product. So the GPL actually won't protect you from
this at all.
It will just result in him producing a poorer, more expensive, less
compatible product -- or none at all. Either way, everyone else will have
fewer (and/or poorer) choices. Everyone loses. Nobody wins.
Note that had he been able to incorporate the GPL code in his commercial
product, he may have passed bug fixes and improvements back to the GPL
project. He would not have had to, of course, but if his product just uses a
GPL component or library (that doesn't compete with the larger product),
there's no reason for him not to. Everybody could have won.
It's always possible he may instead elect to make a GPL'd project. This may
allow him to produce a higher-quality product in less time. It may allow
others to build on his work, and result in more freedom for everyone. He may
make less money, but maybe not. The question of whether the "everybody
loses" or the "lots of people, maybe everybody, wins" case is more common is
an empiric one.
I have seen an awful lot of "everybody loses" cases. I've seen very few
"everybody wins" cases.
DS
next prev parent reply other threads:[~2008-07-19 0:54 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 ` Bodo Eggert
2008-07-19 0:47 ` David Schwartz [this message]
2008-07-19 3:05 ` Eric Furman
[not found] ` <E1KKQd9-000114-IV@fencepost.gnu.org>
2008-07-20 8:34 ` Aleksej Saushev
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=MDEHLPKNGKAHNMBLJOLKAEJDOEAC.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=7eggert@gmx.de \
--cc=announce@fsfeurope.org \
--cc=claire.newman@canonical.com \
--cc=fedora-list@redhat.com \
--cc=freebsd-questions@freebsd.org \
--cc=licensing@fsf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=mharrow@linuxmail.org \
--cc=miod@online.fr \
--cc=misc@openbsd.org \
--cc=netbsd-users@netbsd.org \
--cc=rms@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®