Sadly, it's also free as "please, BigNastyCorp, feel free to take away any freedoms from your users who depend on my work". While BSD may be "more free" according to some, it's the freedoms of the users we are (or should be) protecting. For those, *GPL is the license of choice.
"please GPL, feel free to take my source code, slap the GPL on it and nanana at me when new changes are made that I now can't incorporate"
Look at the whole OpenBSD wireless drivers fiasco that happened. Really us BSD guys have not much to worry about when it comes to corporations (I've had my BSD licensed source code used by big business, and they have donated money to my little dinky project because it was useful for them), we have to worry our source code is not taken by the GPL crowd as they slap the GPL on any changes and suddenly any improvements made I am not able to use eventhough it is still technically Open Source.
From personal experience, BSD becomes GPL hurts WAY more than some corporation taking the code and using it and letting me know either by email or by donating money to my small project.
(The code for the BSD project is no longer online after I found some flaws in it that I didn't want to fix, so please don't ask)
Does it really feel better when it's a multi-billion dollar making that? Does it feel better when they withhold their improvements (if any) from you and their users?
BTW, BSD allows that and BSD proponents insist that's perfectly fine to make proprietary forks of their software, that they don't care about what you make with the software. If you feed offended by what those people are doing - forking your software and giving users extra assurances you don't - maybe BSD should not be your choice anyway.
BSD is for when you don't care what people do with your code. If you wanted corporations to pay for your code, you could have gone GPL and offered a double license option. You cannot build a business on expecting donations from happy generous for-profit corporations. In their position, if I really wanted to pay for your work, I would not donate to your project - I would hire you.
And, personally, I too feel bad about you not being able to incorporate improvements made under the GPL to your code. If I ever made such contribution, I would make sure I also made it to your upstream BSD codebase, under BSD. The license of the project is your choice.
The GPL is designed to ensure the maximum freedoms of developers.
That it simultaneously destroys any hope that those same developers can enrich themselves by selling the software is supremely ironic, as it forces them to live as wage slaves under the whims of their corporate overlords. Thus they gain one sort of liberty but at the expense of giving up other economic freedoms.
Frankly if someone came up to me and said that in their ideal world I wouldn't be able to sell software or build my own software company, I'd want to burn them at the stake for heresy. Fortunately the world is big enough for everyone. :D
Every time society attaches a price tag to an unlimited resource like copies of software, we make ourselves poorer overall by minimizing our benefit from wealth that can't be used up or worn out. In my ideal world, software is developed as work for hire, because it's actually skilled labor that's scarce and needs to be rationed out by the economy. Doctors don't sell medicine, plumbers don't sell pipe, why should developers sell copies of binaries rather than hours of work?
Because selling copies is far more scalable and profitable?
The GPL proposes to give users that right. Since I am in that uncomfortable user position a lot, I am all for it.
For a perhaps overused metaphor, I wouldn't buy a car with the hood welded shut.
Care to explain your reasoning?
> The GPL is designed to ensure the maximum freedoms of developers.
That's why it explicitly prohibits you from using GPL'ed code under proprietary licenses.
No. If you intend to engage in an intelligent debate, you should, at least, educate yourself to a point you actually can.
> That it simultaneously destroys any hope that those same developers can enrich themselves by selling the software
You can always double-license it, MySQL-style. Again, GPL is not for the developers, but for the users. In your case, it's likely you use more software than you create, so, in the end, the GPL actually benefits you despite your own misgivings and misconceptions.
> I wouldn't be able to sell software
Why? What I can't have is a monopoly on the GPL'ed software I sell. OTOH, nobody can have a monopoly on GPL'ed software. And that's a very good thing for the users, who are sure they will have both the software and the technical means to maintain it on the unlikely event I am hit by a bus.
My reasoning is that the GPL is about what you can do with the code the program is based on. USERS don't do stuff with code. Programmers do stuff with code. A user is not going to take an annoying bug in your app and fix it, but (given guaranteed access to the source) a developer might.
> You can always double-license it, MySQL-style.
cough Indeed. uncough
They use it, they trust it works and they hire programmers to do stuff on their behalf.
> but (given guaranteed access to the source) a developer might.
Do you know of any other license that guarantees access to source from every downstream fork?
Could you take said code, remove the license and make it available commercially? Sure, it is your code, but any older or previous copies are still available under the BSD license.
This really does underscore, however, how important it is to license your code carefully. If you want to make it completely free (as in, "I don't care what you do with it" free), use BSD. If you want to make sure that your software is never used restrictively and that it continually promotes the free software ethos, then GPL is a great tool.