That's the whole point of the GPL, whether 1 or 2 or 3. Call it viral
or poison pill if you like, but that's exactly what they intended. And
the GPL has been vastly successful.
> For instance my company is an ISV - we'd never include a Java library
> in our application mix that is GPL3. Sure, we could download and play
> around with SpringSource Application Platform, but if we ever wanted
> to seriously consider using it for our apps, we'd be compelled to get
> on the support contract in order to switch to the other licensing.
What's wrong with that?
You are selling your software for profit. And you want to include
someone else's software in your package. And you don't want to pay him
his fair share of the profit?
> The GNU GPL3 has become used as a club to beat corporations over the
> head in order to steer them into using commercial software.
I understand that parts of the SpringSource Application Platform will be
non-Open Source. See here for Rod Johnson's direct answer to that question:
So there will be parts of the stack that you cannot get as open source,
therefore is proprietary. But that part by definition is not licensed
under the GPL. You can't get it any other way.
The parts that are licensed under the GPL3 is Free Software (Open
Source) by definition. You are welcome to use it under the Free
Software license or a proprietary license. The choice is yours. Nobody
is beating nobody on the head to force nobody to do nothing that they
are not willing to do.
> I have no problem with what SpringSource is doing here. They're in
> business to make money off of their endeavors as software developers.
They are heading towards the acquisition target direction, which I think
is great. It's their product. They can do whatever they want.
> I find it deliciously ironic, however that the GNU GPL3 has become the
> "weapon" of choice for compelling consumers of software products into
> use of commercially licensed software. Richard Stallman's idiotic
> fanaticism is now resulting in exactly the opposite of the ostensible
> goal of GNU. It just doesn't get any funnier that this.
Don't be so quick in making your conclusions. Let's do a thought
experiment:
Imagine you are given the power to wave a wand to make all GPL'ed
software stop working. And you do that. What would the software world
be? No Linux, No Mac OS X (it's all compiled with GCC), No Solaris 10,
No Java, No Apache (they need GPL'ed compilers), No Internet. Everyone
would be using Windows developing software with Microsoft C that costs
$5000/year to license.
RMS is not stupid.
--
Weiqi Gao
weiq...@speakeasy.net
http://www.weiqigao.com/blog/
Don't be so quick in making your conclusions. Let's do a thought
experiment:
Imagine you are given the power to wave a wand to make all GPL'ed
software stop working. And you do that. What would the software world
be? No Linux, No Mac OS X (it's all compiled with GCC), No Solaris 10,
No Java, No Apache (they need GPL'ed compilers), No Internet. Everyone
would be using Windows developing software with Microsoft C that costs
$5000/year to license.
There are probably other flaws to find, e.g. I would expect that Java or Apache did ever rely on a GPLed compiler -- after all the commercial UNIX systems had their own compilers for a long time. And the Internet ain't GPLed either. You seem to miss the whole BSD story, too.
For instance my company is an ISV - we'd never include a Java library
in our application mix that is GPL3.
what I find to be a delicious irony that proves my point.
It's just a little thought experiment. Nothing serious. It has a lot
of holes in it. But it's worth spend a few brain cycles on it.
> The fact that good software exists
> written under some licence does not mean the licence is good -- I'm
> pretty sure if the GPL wouldn't be there, Linux would have had some
> other OSS licence or maybe even be in the public domain. It would still
> be working, though.
My point is not to prove that the GPL is good. I just want to point out
the success of the GPL and the brilliancy of RSM's strategies. To
counter the idiocy tag that Roger was trying to put on him.
> Of course you can argue that the GPL was part of the success story of
> all these products (something I'd rather not argue for or against), but
> please don't confuse products and their licences.
>
> There are probably other flaws to find, e.g. I would expect that Java or
> Apache did ever rely on a GPLed compiler -- after all the commercial
> UNIX systems had their own compilers for a long time. And the Internet
> ain't GPLed either. You seem to miss the whole BSD story, too.
If I take all GPLed code away from BSD, do I still have a functioning
BSD? (This is a genuine question. I don't know the answer as I'm not a
BSD user.)
We are getting way off topic for the Java Posse. I'll take the next
round of darts without throwing them back.
If I take all GPLed code away from BSD, do I still have a functioning
> Of course you can argue that the GPL was part of the success story of
> all these products (something I'd rather not argue for or against), but
> please don't confuse products and their licences.
>
> There are probably other flaws to find, e.g. I would expect that Java or
> Apache did ever rely on a GPLed compiler -- after all the commercial
> UNIX systems had their own compilers for a long time. And the Internet
> ain't GPLed either. You seem to miss the whole BSD story, too.
BSD? (This is a genuine question. I don't know the answer as I'm not a
BSD user.)
We are getting way off topic for the Java Posse. I'll take the next
round of darts without throwing them back.