Is preventing someone from taking away your freedom taking away their freedom? Technically yes. But it's a worthwhile "loss".
They're just clickwrap EULAs, since you can't enforce the restrictions they add on top of the GPLv2 via copyright law.
Sure you can. Under copyright law, you can't distribute copyrighted code without permission. You also can't distribute derived works; binaries produced by your compiler. The GPLv3 grants everyone permission to copy, compile, and redistribute, as long as they give others the same permission, promise not to sue the people they give the code to, and promise not to ship the code on hardware that can't run modified versions of the code. That fits perfectly into the framework of copyright law. If you don't like the conditions of the GPLv3, you fall back to copyright law -- you can't distribute binaries or modified versions at all.
EULAs rely on a much shadier principle; that you "redistribute" a copyrighted work when you copy it from your disk into memory. Copyright law says, the lawyers reckon, that you can't make that copy unless you are given permission. You are given permission by following the EULA.
You can see that this is not quite the same as the GPL because of the scope. EULAs say copying is how your computer runs programs. The GPL says copying is making a copy for your friend. Much more solid.
Anyway, if you don't like software licenses, don't use one. I like the GPL, though, because I want people to give me back what I gave them. Nice people will do that anyway, but not everyone is nice. So the GPL clearly spells out their obligations to me, and lets them make an informed decision as to whether or not they want to modify and redistribute my software. The nice people follow the rules anyway, so the GPL makes no difference to them.
The GPLv2 operates solely within copyright law — it hinges solely on distribution of the work itself and nothing else. The GPLv3 gets into contract-like territory, with the patent grants and restrictions on hardware.
I do think that the GPLv3's tivoization clause is operating on the same shady principles as EULAs: if it's not a contract, then they're effectively claiming that a digital signature is a derivative work!
I'm a nice person that doesn't like the implications the GPLv3 has for Freedom 0.
They're just clickwrap EULAs, since you can't enforce the restrictions they add on top of the GPLv2 via copyright law.
Sure you can. Under copyright law, you can't distribute copyrighted code without permission. You also can't distribute derived works; binaries produced by your compiler. The GPLv3 grants everyone permission to copy, compile, and redistribute, as long as they give others the same permission, promise not to sue the people they give the code to, and promise not to ship the code on hardware that can't run modified versions of the code. That fits perfectly into the framework of copyright law. If you don't like the conditions of the GPLv3, you fall back to copyright law -- you can't distribute binaries or modified versions at all.
EULAs rely on a much shadier principle; that you "redistribute" a copyrighted work when you copy it from your disk into memory. Copyright law says, the lawyers reckon, that you can't make that copy unless you are given permission. You are given permission by following the EULA.
You can see that this is not quite the same as the GPL because of the scope. EULAs say copying is how your computer runs programs. The GPL says copying is making a copy for your friend. Much more solid.
Anyway, if you don't like software licenses, don't use one. I like the GPL, though, because I want people to give me back what I gave them. Nice people will do that anyway, but not everyone is nice. So the GPL clearly spells out their obligations to me, and lets them make an informed decision as to whether or not they want to modify and redistribute my software. The nice people follow the rules anyway, so the GPL makes no difference to them.
Are you a nice person?