Re: wine-license digest, Vol 1 #140 - 9 msgs

[email protected] wrote:

> THEN DON'T USE GPL CODE IN YOUR SOFTWARE.
> 
> If the competitive advantages of keeping your code secret outweigh the
> difference in cost of being able to leverage existing GPL code, then write
> your program from scratch and keep it proprietary!  If the competitive
> advantages DON'T outweigh the cost savings of leveraging existing GPL
> code, then don't whine that the GPL comes with strings attached, because
> your application wouldn't have gotten written anyway if the GPLed code
> hadn't been there!

And, BTW, I can potentially make a boatload of money if I can sell you a
proprietary library that provides enough of the functionality of the GPL
code at a price that makes it worth your while to write that software,
since you're probably not the only one faced with this problem.

You see, if the GPL becomes dominant, there becomes a demand for
proprietary/commercial implementations of GPL code, just like there
currently is a demand for GPL implementations of proprietary/commercial
code.  The two markets complement each other nicely.

In fact, in the above scenario it would be the BSD/X11 license that is
interfering with the _library developer's_ ability to make a profit off
of their code.

GREG