Slashdot Mirror
Leaving the GPL Behind
olddotter points out a story up at Yahoo Tech on companies' decisions to distance themselves from the GPL. "Before deciding to pull away from GPL, Haynie says Appcelerator surveyed some two dozen software vendors working within the same general market space. To his surprise, Haynie saw that only one was using a GPL variant. 'Everybody else, hands down, was MIT, Apache, or New BSD,' he says. 'The proponents of GPL like to tell people that the world only needs one open source license, and I think that's actually, frankly, just a flat-out dumb position,' says Mike Milinkovich, executive director of the Eclipse Foundation, one of the many organizations now offering an open source license with more generous commercial terms than GPL."
Editor's note: InfoWorld tried to interview Richard Stallman, who runs the Free Software Foundation that created and manages the GPL, on this issue, but he demanded control of what we published, so we declined.
I LOLed.
Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
"...one of the many organizations now offering an open source license with more generous commercial terms than GPL."
How can there be people yet that confuse the terms? Repeat with me: GPL license is commercial-friendly, GPL license is commercial-friendly, GPL license is commercial-friendly. (I can sell the software, sell services... in the end, commercial revenue). Didn't you want to say "proprietary" instead?
They don't claim copyright, the just want something in return. You use my code, I get to use your code. A simple barter system. You don't like the deal, don't use the code.
If you invent the knife and then tell me I can only use it if I don't draw blood, why give it to me? I can decide if I am fighting off a wild beast to save my children or carving art with it.
Perhaps I think it is the wild beast's right to eat your children. Would you still rather carve your art with a splintered rock? The point at hand, however, is not what you may or may not use the knife for; it's how you can modify it, and if you need to show other people how to do that if they think your modifications are useful.
If I come up with an easier way for making knives, and show you how - I'm sharing my idea with you, for whatever reason; but let's just say that in whatever society or tribe this is, we live better if more people can have knives. What would piss me off, in this situation, is if you came up with a way of strapping my knives to a stick to fight with less danger to yourself; but wouldn't show me how.
If you then start selling your 'my-knife on a stick' (okay, let's call it a spear) because you can make knives easily using my process; but hide how the knife is reliably attached, you've created a competitive advantage for yourself based on my work.
Lets say that a third person comes up with a stronger, lighter stick. He wants to put a knife on it, to make Spear 2.0, and I show him how to make the knives; but he doesn't know how to attach them. I don't know how, either. In fact nobody does; but you.
Now, we have the opportunity to make a better weapon for everyone, but nobody wants to ask you how to bind the knife to the stick, because you're likely to rip off the new stick idea as well, and you probably wouldn't show us the right way, anyhow, because you want to be rewarded for other people's work.
The rest of this really hinges on you. You could share the information, and we'd all live better because we'd be the best armed tribe in the region. There'd still be work making the spears; and since you've been doing this the longest you can probably still make the most money or whatever if you want.
You can derive whatever moral from this you like; but the upshot is that ultimately we're going to rally the tribe to snatch you in your sleep and torture the information out of you with blunt sticks and short knives; err, I mean, get everybody to use a system of interoperating open source software components.
In many cases they could also use the LGPL (provided they can cleanly separate the proprietary and open components), and I have no idea why they do not.
Because the LGPL means you have to constant work within a legal framework that it sets down, whereas BSD licences give developers the freedom to ignore the legal implications of what they are doing and just get on with their job. Laywers are expensive and to constantly have to consult specialist legal consul just to ensure you are on the right side of the LGPL quickly pushes a projects costs up. In the commercial world the BSD licence gives the most freedom to the original creator of the project, yet still lets outside parties contribute.
You might argue that outside would never contribute to a BSD project as there is the possibility their work could be used in closed source projects but that is not the case since plenty of people do. Some people might be put off, but that is a trade off for having the freedom to adopt a different licencing scheme in future without having to trace every contributer to your project and get them to sign a waver saying they will not enforce the GPL over the code they comitted to your project.
I dont read
You could put it like this : his words are open, so he wanted the article to have the same openness so he could correct obvious mistakes. So RMS open source words are viral, infecting articles with their openness :-)
I never could decide wether he was a genius or a nutjob, so I figure he's probably both.
If all else fails, immortality can always be assured by spectacular error.
BSD license is also good for people who just don't care about "free riders" or not. They've got a good product, if some leech comes along and sells their own versions and mods, then so what?
If TCP/IP was originally GPLed, the protocol would probably not have taken off. BSD licensing (or public domain) promotes standards propogation. GPL encourages reinvention of the wheel, when someone decides that (heaven forbid) they want to be paid for their work (be it huge code additions, or just packaging up free code in a nicer package, or whatever).
Me? I'd much rather there was freely available BSD code for whatever problems have already been solved. Commercial products would be free to implement this well tested, standards compliant code and provide additional features that others may or may not be interested in. Those not interested in paying could take the base, well tested code and write their own pretty interface (or whatever) for it.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Then again, some folks want to use a tiny bit of code for processing XML files or handling a networking connection in a way that will work on all of their target platforms within an enormous body of code they've had to write by hand which does far more than just send generic packets or read a single data format.
Some folks would be OK with sharing the modifications to that code that were required to make it work with their program, and even the interface used to make it work within their code including the memory structures and processing functions.
However, they don't want to give their entire product away for free because they used a library which used to be delivered under those terms, was switched to GPL, then security vulnerabilities were found which will never be patched within the LGPL versions which make it unethical to use the original code without fixing the vulnerability in the internals. Then those folk are righteously fucked, as any bug fixes will essentially require use of code that is now licensed under a different license which will now infect the rest of their product.
Too bad for them? That seems to be the general idea. But not everybody has the luxury of being able to give away their code for free to the entire world (and, in fact, it may be illegal for them to do so).
Because the code may actually exist somewhere else other than GPL code. If it does not exist, there may be people elsewhere working to bring it into existence under a different license. That's a lot different than having hundreds of companies reinventing the wheel in isolation.
For instance an older product I was on wanted to use internationalization. The GNU libintl and gettext programs seemed very good for this purpose, and it actually is. The tools can all be used off line to create and manipulate the databases and they're very handy and solve a tricky problem. But the library we had to statically link to for looking up strings was GPLd. I would have taken a too long to reverse engineer an equivalent library (even longer if you try to use a chinese wall). Without that library all those external FSF tools were pointless. But there was BSD code for the same library; someone else had reinvented the wheel and made their work available for all, and that library was maintained.
Whereas if I had reinvented the wheel, I seriously doubt the company would have let me make it available to others even though we weren't a software house. I definitely would have had no time at all to support or maintain it for others.