More freedom to who? Users, distributors, maintainers, vendors, service providers? You can't guarantee complete freedom to each of them simultaneously.
For example, allowing distributors to do everything they want (e.g not providing source code) will prevent users to do everything they want (e.g modifying the program). So it makes no sense to talk about which license "offers more freedom".
So, let's stop saying imprecise things like "GPL code doesn't give me freedom because I can't use such code in my proprietary software". The free software movement is about protecting the freedoms of the end users first.
In the same way that a a very inexperienced french candidate for presidency is claiming that he will "liberate France by the work", ear "deregulate the working laws and make possible for companies to get rid of the employees whenever they want without any compensation". Freedom for employers.
When a project includes code from another project (be it GPL or MIT), it is creating a new work under copyright. What GPL does is hold the developer ransom with a lighter over the GPL code, in order to guarantee the new work is distributed to other people with the same restrictive license. It just means that code under GPL is orders of magnitude less valuable to the world than code under less restrictive licenses.
It's not just about proprietary software that can't put GPL code into their software, but software that's released under less restrictive licenses as well. If code is GPL, I just stay away.
If you define free in terms of users and individual developers, GPL is absolutely more free than BSD/MIT, but if you define it in terms of software development houses, MIT is much more "free" than the GPL indeed.
The argument against the GPL having restrictions on what you can do with the code as to not take away freedom, is like the U.S Constitution having restrictions on what the government is allowed to do to restrict your freedom.
Nobody would argue that the right to free speech is restrictive, because it takes away your right to restrict free speech, or would they?
While we're voting with our feet, I don't contribute to BSD projects unless I'm paid to, because it's mostly feeding parasites.
The most-installed kernel in the world is GPL-licensed. I'm not sure how it could possibly be orders of magnitude more valuable.
> What GPL does is hold the developer ransom with a lighter over the GPL code
It's not a 'ransom' when the ticket price is clearly displayed for all to see. If you don't want to play, that's cool, find another sandpit to play in.
Like it or not, the GPL moved the needle back towards end-user friendliness, and without it and it's knock-on effects elsewhere, being a developer today would be a much more frustrating experience.
GPL conditions are primarily concerned with freedom from external restraint, such as patents, proprietary licenses and DRM. Negative liberty, which is the freedom from interference by other people, is the other side of the coin from positive liberty, ie the possession of the power and resources to fulfil one's own potential. All FLOSS licenses has positive freedoms, but not all grant negative freedom.
It's up to you what 'freedom' really is.
For me, I wish my smartband had more features than it does now. I wish my non-smart phone vibrate when the opponent attends the call. Lots of my wish (and many others) won't be fulfilled as long as there isn't an easy way to modify the underlying software/firmware. I call that 'freedom'. Most of these limitations comes from the software/firmware in it.
[AL]GPLv3 assures the freedom to its users. And every person is a user. A developer is a user of IDE, compiler, build tools, OS, etc.
It is the freedom to control what [s]he own and not to be in control.
I'd love to have the freedom to modify the software in every gadget I own. But the $40 digital toaster oven with absolute crap firmware coded by idiots doesn't even have a USB port or any way to attach it to a computer; it's probably got its code permanently burned into ROM and isn't even software upgradable even with the right hardware.
If it were programmable, it probably would have cost 5x as much.
Say it's a device that already supports updates, like your smartband likely does. By locking down, say, a smartband, you've made it much easier for your support personnel to be able to answer questions -- and they won't have to say, "Sorry, you've modified the device, so I can't help you." And they won't have to field questions from hackers who are trying to follow the poor instructions that engineers pieced together on how to rebuild the firmware.
And that's if they even have the right to distribute the firmware to begin with. Just because your smartband manufacturer wants to do the right thing (in this theoretical universe) and make it hackable, doesn't mean that the chip manufacturers are happy with that. So they might need to switch to another, possibly more expensive chip.
And that means the goal of "hackable" needs to be a design goal from the start. Shortcuts they might have been able to make with a closed system are now off the table. You've added another constraint to the design, and every constraint takes time. And money.
Advocate that companies produce modifiable devices, sure. But don't pretend that it won't increase their cost at some level. It's not ethics; it's simply good business to lock down products that 99.9% of users won't try to hack.
And I'm a fan of hacking devices. I just can see the other side of the argument.
You can make the argument that it's too financially expensive for most companies to make their devices more modifiable, but that same argument cannot explain why people are banned, by risk of government punishment, from decrypting their programs, which would be the first step to investigation.
Because they're shortsighted and afraid, in short. Legacy companies feel that control is crucial.
But GPL and other Copyleft software requires you to make the code modifiable. That's an expense most companies don't want to take on. Hence, companies avoid GPL.
Only if you consider 'freedom' to include the right to take something and make it closed source with or without changes. Only if you consider 'freedom' to include the right to restrict end user freedom.
The GPL protects the freedom of users. If I license something as GPL then that means I'm saying "I want anyone to be able to use this, and if you want to modify and/or redistribute it you can, but only if you continue to respect users' freedoms as much as I have."
The only person 'messing the language' are the people that turn every discussion of free software into a discussion of whether 'free software' or 'open source' is better terminology, and in my experience that's far more coming from your camp than Stallman's these days.
My point is that "freedom" is a messy concept, and the freedom to do one thing (punch somebody in the nose, or to make proprietary software) is often at odds with the freedom to do another (go about your business without being punched, or to control the software that affects your life). That's not RMS twisting words, that's just an awkward philosophical truth.
I guess you could say that the term "free software" is biased because it emphasises society-wide freedoms over personal freedoms, but I think it fits nicely alongside more widely held ideas like "only police should be allowed to fight crime" and "politicians should not write laws that directly benefit themselves". Both those ideas significantly limit personal freedom, yet they're very important parts of a free society.
It's also worth noting that it is not only Stallman's FSF that uses this definition w.r.t intellectual property nowadays. Lessig's CC adopted the same terminology for their share-alike license (-SA), which has the goal of preserving freedom, while -NC or -ND are considered non-free because they contain restrictions not related to this purpose. The same is true in the greater free-culture community and academic contexts from my experience.
In practice the "freedom" is exclusive to a highly educated and exclusive technocracy. The same freedoms are not available to the general public.
This may seem pedantic, but IMO it undermines the argument about software freedom, because Stallman has never shown the slightest interest in making software that the general public can modify, or in designing, promoting, or doing anything at all to encourage the existence of such software.
The idea that if you want to promote software freedom you need to make tools and systems that ordinary people can modify - preferably without learning Emacs - doesn't seem to have occurred to him. It seems that in Stallman's world the public are supposed to become MIT-grade hackers before they can earn their freedom.
You could argue that software is hard, and that's just how it is. But I'm not so sure that's true. It's not obvious that the hardness of software isn't a side effect of the culture around it, and not something unavoidable in the process of development.
The reality is that there has been almost no serious CS research into making accessible user-modifiable systems. FSF would be more convincing if there had been at least some token effort in that direction. But instead FSF has always promoted a rather old-fashioned and nostalgic view of computing, where everything happens on the command line, and development means hand-editing source code and running a build system to create a local binary.
That was more or less the only model around in the 1960s and 70s, but things have moved on since then. Unfortunately the FSF mostly hasn't.
Given that, the question is - what does software freedom mean to users now? If source code doesn't actually equal freedom - what does?
That's unfair.
Let's say we're talking about vehicles rather than software.
The liberty to share information, to modify one's own vehicles, and so on is valuable even without a research program to educate every commuter about engineering or make motors modifiable by someone with no special knowledge.
The benefits of software (or vehicle) freedom extend to every user even if they aren't directly involved with software engineering. As a non-programming user, you can find someone who can help you modify programs. You can also begin to learn yourself, as I and many others have done.
Free software is itself an enormous library of learning resources simply because you can study its source code and reuse its components.
To talk about a "highly educated and exclusive technocracy" in this context seems pretty overblown to me. Yes, efforts to make programming more accessible are very cool. But any motivated kid with a computer can get into coding right now. With the availability of free software, they can study working software packages written by experts, for free.
The GNU project was a pragmatic initiative to ensure the existence of a free operating system mostly conforming to the typical Unix-like environment. Call it old-fashioned, but even iOS is built on such a foundation.
I agree that eliminating barriers to entry for newbies is important, but basically I think it's long-term future work and that the FSF is right to focus on the fundamental freedoms for hackers.
This is not true. In his Emacs paper he specifically mentioned that people who were told that they could not possibly be programmers were in fact programming by modifying Emacs. He also pushed for Emacs to gain word processing features and was ridiculed for that.
I'm wondering what you have in mind by user-modifiable systems. For example, KDE and Firefox are free and allow for quite a bit of user-customization without any programming knowledge. At some level you would naturally have to write code.
I recently came across this interview and thought it was well done. Stallman responded to a similar question: https://youtu.be/NB8mCcLRxlg?t=59m55s
No, because freedom of modification and the guarantee that such modifications must also be released with a similar licence means everybody, programmers and non-programmers, benefit from that freedom, directly because they modified the source code, or indirectly because they can freely use that modified software, respectively.
Define "general public". As far as I remember, Stallman was a MIT hacker working on stuff like compilers. It is not exactly the kind of thing the "general public" want to know about.
He did some significant parts of Emacs. 30 years after it's creation, this piece of software still exists, has been modified by thousand of people, including non-programmers.
Stallman is not only a software hacker. He is a "hacker", and hacked a piece of law that is a serious little trick that actually created a revolution. Torvalds hacked on the hardware/kernel part under the basic law hack and things started. That's a real success!
The arguments about terminology "GNU/" VS "Linux" are fun but I think we underestimate the law hack.
What do you think "freedom" is? We are here because we are not free. And that is called "freedom". :)
Freedom may be considered as a set of values that can be exercised on every human. So that is very limited. Say like "I wish not to be harassed in the public." So that means, "I shouldn't harass someone else in the public." If you say you need the second, and not accept the first, you can't call it a "freedom" in a communal sense.
For the record I'm not an RMS-ite and I don't actually mean to compare proprietary software with slavery.
It's a title for a concept, it isn't a redefinition of the word "free." It is always capitalized. Software can't even be free or unfree in any way other than gratis, unless you're talking about software behind a restrictive firewall - software isn't a person or an animal, generally isn't thought of as having agency or desires, and couldn't care less (or more) about the aspects of whatever license it is distributed under - licensing is for people.
It's unbelievable that this could be the main obstacle in accepting a philosophical and political idea that has material effects on the human condition. What do you do when a "stop" light turns green?
"Free Code" means the code is free as in free beer. You can get it, consume it and share it with friends. Once tasted, you can start a brewery and imitate the flavor if you want.
What does the GPL prevent you from doing?
As a user, nothing. As far as I (a user) is concerned, Mozilla's MPL/GPL, bash's GPL3 and VSCode MIT licenses are all equally free (I can use them and distribute them).
So what problem do programmers have with GPL?
You can't make a derivative closed source work.
So you want to make a non-free work, fine. I'm not a GPL-or-bust guy.
But are _your_ programs free?
That's not it. Your license has to be GPL in order to use any GPL code. I try to make the stuff I do on my personal time under the MIT license, which means I can't use GPL code, but GPL code can incorporate my code. Tell me which license is more free now.
Also, it completely disregards the scope of things. If I incorporate a GPL library into my software for say JSON parsing, then it means my entire program must be GPL. Thankfully most libraries aren't GPL but LGPL.
The other thing is that you can't use proprietary libraries in your own code that has been infected with GPL. If you want to develop your own software that incorporates GPL code and even release it to your users, it's impossible to link against proprietary libraries.
That's not how the GPL works. The GPL requires that you release the entire work under the GPL, but it does not forbid you from additionally releasing the parts you wrote under other licenses. So you can release the parts of the code you own under the MIT, as long as you also release the whole work under the GPL. [0]
> The other thing is that you can't use proprietary libraries in your own code that has been infected with GPL. If you want to develop your own software that incorporates GPL code and even release it to your users, it's impossible to link against proprietary libraries.
This is exactly the point of the GPL, and what, in my opinion, makes it more free than permissive licenses: GPL code will never restrict the user's freedom. Software that uses proprietary libraries is not free software, and so it is perfectly reasonable for it to be GPL-incompatible.
[0] https://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense
Sometimes I suspect the main programmers for Apache2/BSD/MIT licensed works actually hope their works get used by the big guys so they can get employment there.
That's why I've never heard any BSD guys getting upset at MS for ripping off their work, while getting upset at Linux for doing the same.
I think there's a widespread misconception that you have to relicense code in order to combine it with the GPL. You don't. The code can retain its license, because its license allows it to be used with the GPL.
Saying that you have to relicense MIT-licensed code under the GPL is like saying that you have to grant a special proprietary license for Apple if they want to use your code in macOS.
That's a pretty big exception, which reverses your conclusion. It's like saying "not true not everyone can buy Lamborghini Aventador - everybody can, as long as they have half a million dollars to spend!" That's kind of the point that turns your "not true" into false.
> Pretty much all of the popular free licenses are compatible with the GPL.
https://en.wikipedia.org/wiki/Comparison_of_free_and_open-so...
Just look at the "GPL compatibility columns". Even GPL2 is not compatible with GPL3 without a special "or later" clause, which is all too easy to miss.
> The code can retain its license, because its license allows it to be used with the GPL.
But if you want to distribute the mix, you'd have to abide by GPL conditions.
It's not. Most of the anti-GPL free software advocates are using compatible licenses, such as the MIT or BSD licenses, and they are already following all of the conditions of the GPL, since they are distributing source code.
> But if you want to distribute the mix, you'd have to abide by GPL conditions.
Almost everyone is already abiding by the GPL conditions when they are distributing MIT-licensed code. The only real concern about violating these conditions is to not distribute source code. If you have no intention to distribute non-free software, you should have no concern with the GPL.
I just cannot understand, try as I might, why anyone would have a problem with the GPL while at the same time eschewing non-free software. If you are already doing as a matter of course what the GPL is asking you to do, why do you object to being told to do it?
Yes, this is my main obstacle accepting RMS. In my opinion, he took the word "free", made a term "free software", and described it in accordance with his agenda, while what he advocated only partially conforms to the meaning of the word "free" or "freedom". There are certainly licenses offering more freedom than GPL v3.
Therefore I myself do not even recognize this term "free software". I am more than willing to discuss RMS ideas, I agree with many of them, but let's stop messing the language first.