
Frank Atanassow writes:
Some people don't see it that way. They would say that the GPL is the _less_ restrictive license because it ensures that everybody benefits (equally) from everybody else's improvements. From that perspective, companies benefit also since they may use and improve the code, provided they "publish" it. Will they lose some potential revenue that way? Possibly.
As I understand it, the situation is worse than that. The mere existence of GPL code poses a threat to commercial software: if a programmer happens to read some GPL code and then goes on to use similar techniques in proprietary code, the owner of the proprietary code is in a legally difficult position. So not only is a programmer working on GPL code not generating any revenue, they are potentially threatening the intellectual property that the company already owns. Better all round for them just to avoid GPL code altogether. Cheers, Simon

On 2001-05-28T16:14:29+0100, Simon Marlow wrote:
As I understand it, the situation is worse than that. The mere existence of GPL code poses a threat to commercial software: if a programmer happens to read some GPL code and then goes on to use similar techniques in proprietary code, the owner of the proprietary code is in a legally difficult position.
Really? I've assumed that GPL only deals with copyright, and techniques one uses in code are matters of patents and trade secrets. Here's a message on what license to use, from gnu.misc.discuss: http://groups.google.com/groups?hl=en&lr=&safe=off&ic=1&th=8e757ec573e5498,15&seekm=rjzoeoifn9.fsf%40ssv2.dina.kvl.dk -- Edit this signature at http://www.digitas.harvard.edu/cgi-bin/ken/sig
My SUV is bigger than your bike. Stay out of the damn road! Kiss my reflector, SUV-boy I'm too busy sucking on my tailpipe, bike dude.
participants (2)
-
Ken Shan
-
Simon Marlow