A new source of anti-GPL FUD [LWN.net]

A new source of anti-GPL FUD

Posted Nov 23, 2003 11:44 UTC (Sun) by rev (guest, #15082)
In reply to: A new source of anti-GPL FUD by fLameDogg
Parent article: A new source of anti-GPL FUD

Ok, maybe the OP was trying to say the following: this programmer of his can screw his former employer by releasing a reimplemention of his former employers' offering under the GPL. Assuming this is what the OP was trying to say, I still fail to comprehend how this is somehow a GPL specific problem. This programmer could have taken revenge on his former employer just as well by releasing his package under a BSD license, a X11 license or under a public domain license or some other source license. In fact, this programmer could have screwed his former employer equally well by releasing his software in binary only form under some license for little or no charge ("Cutting of their oxygen supply" this is called in the trade). The core of his case, if this is indeed what he is trying to say, is not that the programmer releases his product under the GPL but rather that he offers his own product for little or no charge.

I still do not get it. I still don't understand how this problem (what problem exactly?) is somehow related to, or a consequence of the GPL. I honoustly fail to understand. Please OP (Robert?) explain.

(Log in to post comments)

A new source of anti-GPL FUD

Posted Nov 23, 2003 20:30 UTC (Sun) by ccchips (subscriber, #3222) [Link]

You know what?

Think Netscape -> Internet Explorer.

It's worth pointing out that both of these were being distributed under a clearly non-free license at the time. The dirrerence was that Microsoft decided to "cut off" Netscape by distributing the tool free-of-charge to *everyone*, whereas Netscape had some requirements for corporate users to pay, and hoped that home users would pay once they decided they liked Netscape (indefinite evaluation period.)

What I can't understand myself; why anyone with any sense pays attention to some of these lawyers' idiocy.

As far as using the GPL to get back at a former employer, I agree that it's not all that formidable of a weapon. All the employer needs to do is to start releasing and distributing modified versions of the employee's program, and then offer better services andd value-added products (maybe in binary-only form, for a fee,) that compliment the GPL's product.

A new source of anti-GPL FUD

Posted Nov 26, 2003 4:13 UTC (Wed) by stefanwagner (guest, #17209) [Link]

The example want's to show a problem of the company, of getting a buisiness-damage (I'm sorry for my english).

Of course other companies may produce better, cheaper, maybe open source programs, which take the others company customers over.

Think of an baker. Baker man is baking bread.
He's got a good idea of a new kind of bread, is fired, and produces the bread in another bakery for less amount.
Or another company can immitate that bread.

Of course it is a problem for the first company.
But it's not a crime, while no contract guaranteed the unique usage of the idea.

How is it possible, that there isn't just one company producing cars?
Is every engineer a criminal?

If a company includes just a little piece of open source code in their proprietary software, there shouldn't be too much costs, in replacing it by code developped by own programers.
If the open-source is the biggest of the software, the effort in building this software was too small.

Of course, a programmer is responsible for not stealing code - whether open source or not.
Of course it's harder to steal closed source code, but it's not impossible - think about decompilers and dynamic link libraries.

If a company for canned meat, aka spam, solds cans where their stuff included stolen meat they have the same problem.

The lawyers made the fault to assume, that the GPL might be infecting all the other code, mixed with (stolen/ misused) open source.

Of course, if you sold open source, due to a criminal act of your employee, you have to remove the open source code, and find an alternative.
This should be possible for nearly any case.
If this is too expensive, you either stop the projekt, or license it under the GPL.

But a company is responsible for the acts of their stuff.
It may demand compensation from the programer.

That's my opinion.