Is GPL Licensing In Decline?
GMGruman writes "Simon Phipps writes, "As Apache licenses proliferate, two warring camps have formed over whether the GPL is or isn't falling out of favor in favor of the Apache License." But as he explores the issues on both sides, he shows how the binary thinking on the issue is misplaced, and that the truth is more nuanced, with Apache License gaining in commercially focused efforts but GPL appearing to increase in software-freedom-oriented efforts. In other words, it depends on the style of open source."
Didn't we have this story last week?
Like it or not, but the fact that GPL is prohibited in many app stores is probably what discourages authors of FLOSS from using it as their license. Some authors may also feel that they don't want to use it even if it works fine for them now since they don't know what will happen in the future, as contributions are accepted from other authors it becomes much harder to change license. It's not 1991 anymore.
I've had recent occasion to talk to a few SAAS providers and other software producers who are employing OSS tech in some of their products and the consensus was the GPL was too constrictive, so their using other schemes. I'm also noticing others around the web sticking to GPL 2.0, and dismissing 3.0. I'm just a messenger, just what I've seen.
Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
Personally, I prefer the BSD licenses. There's more freedom in it. Although, I can see why people like the GPL & Apache licenses, I think they're a little too restrictive.
Who'd a thunk it?
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
Personally, I think the whole open source gig is fading away. The next generation of programmers have been raised to live and program in flashy iDink walled gardens and have neither the interest or the inclination in releasing or collaborating on code.
In their world, code is something that is packaged into an app, approved by Apple, and then sold for profit. It is not something which can even be freely compiled and run on their devices, let alone shared and co-written.
Ultimately computers and the Internet are growing up, moving out into suburbia, and accepting pre-packaged convenience over creative potential. People want shiny and slick, and really couldn't care less freedom, code, control, or innovation. There's probably an App for feelings like that anyway.
The Internet is becoming squaresville, one settled Mac user at a time.
May the Maths Be with you!
To restate the obvious:
There are two paradoxical possible twists to an open source license.
1. The user is allowed to use the source as part of a closed source product (which is a kind of freedom)
2. The user is obliged to make derivatives available as source (which ensures the greater freedom of other users/developers) (this is a restriction on the actions of user 1)
Neither one is complete freedom. They are both giving up something - the possible work of the downstream user or the business motivation of the first user.
The GPL's origin is in RMS' desire to be able to modify software that was produced by companies. It takes this to the extreme, basically by prohibiting closed source products based on GPL.
The benefit of this is mostly to developers, and within that, to developers who are independent. Software companies share code / secrets a lot as part of business, but under NDAs. The FSF has as a slogan "you deserve software that is free" but how many users want to exercise the freedom to modify and recompile their software?
More and more, FOSS is produced in a dual stream approach - Redhat/Fedora, Jboss community/pro, other things work this way like Jasper reports etc
The reality of this is that the code that is run in production is not "free" in an active way. When you pay for a supported version of RHEL or whatever you do not generally modify anything very deep inside it and then demand support for your modified version. The fact that you are paying for a supported version is a disincentive to using a modifed version, your own or anyone else's.
Also consider that the Linux kernel is largely developed by people working for IBM, Suse, Redhat, etc.
So while the lone developer wanting to add his improvements to the commercially produced and defective printer driver is a convincing story to argue for the GPL, the reality as it is today is different - it's more like the millions of Linux users who wish their hardware was supported but do not produce a driver for it. And I know they may not have access to the necessary information from the hardware maker, etc. Still, the number of people able and motivated to write OS-level code is small. I know I don't know enough to do it.
Nonetheless, the existence of (mostly) GPL OSes is an amazing thing. The access to knowledge for developers that that provides is awesome. But a lot of the requirements to stay GPL-pure do not sound like freedoms to me- requiring you not to buy certain(most) products, visit certain sites - it's ironic when, in the name of freedom, your freedom to act as you wish must be limited.
You ask me: "Is GPL Licensing In Decline?"
I ask you: "Who Cares?"
if the GPL fits your goals (personal, business, etc.), then use it.
If the GPL doesn't fit your goals, then don't use it.
If the whole world goes GPL or I am the last person on Earth releasing code under the GPL license .. does it really matter, if we're all meeting our goals?
Many banks and other companies that received threatening letters from SCO and MS salesmen have anti gnu or freeware policies in their organization. A famous Canadian bank even licenses for an obsolete version of SSH because BSD *might* be gnu. Funny, that the corporation just downloads the BSD one and repackages to the customer as its own for $$$.
Lawyers are afraid of it in big companies after several court cases with companies like Netgear being accused of copyright infringement for including Linux without the source in some of their embedded products.
I could turn this into a BSD vs GPL flameware but wont. There are many such as myself who feel comfortable using free software at work but would feel better modifying and shipping BSD versions which are more business friendly to customers and suppliers. Remember you are asking the company to ship its crown jewels away if they license it with GPL. It is true it may protect you agaisn't getting ripped off, but you have no way to know for sure.
Businesses do not like risk or to give away free things. They own them if they paid for the labor so why the risk?
http://saveie6.com/
I don't think so. I have found that BSD based software tends to lags in "bleeding edge" features (not that is is better or worse) since the people that use, customize and enhance BSD licensed software are not legally required to disclose these changes as it is required by GPL.
Yeah, it's true.