Daniel hits on a key aspect that always bothered me: who the real "users" are. The GPL doesn't affect me as an end user, but it does affect me significantly as a developer, especially if my intent is to potentially create proprietary software products.
Conversation
You are free to do so with software that is not licensed in a way to propagate and protect Software Freedom.
It simply is not a policy goal for the GPL to enable you to create software that does not offer Software Freedom to those you give copies...
1
1
It can't protect software freedom when it restricts freedom to use the software for whatever you want. I don't see much difference from these new restrictive non-commercial licenses and other restrictions. It's a difference in values with same kind of approach to enforcing it.
1
Many other people don't see the difference either. Tolerance for GPL leads to tolerance for these new restrictive licenses. The vast majority of people who are not familiar with any of this stuff aren't going to buy into the Free Software movement's claims that it's different.
2
2
I find the take of the GPL as restrictive quite novel.
2
1
You may not like it, but the GPL *is* a restrictive license, and no amount of justification that has been repeated ad nauseam over the years changes that. "it's easy to comply with" "it's for the greater good" "it's a compromise" "proprietary software is evil" and all that jazz
2
I think the discontent with the (not quite positive) label of "restrictive" for the GPL family is that its restrictiveness is at a meta level: it restricts one's rights to further limit/withhold code distribution.
In contrast, "permissive" often allows those limitations.
2
1
You're misrepresenting the goal of the GPL as the reality of the GPL. It's inaccurate spin. It heavily restricts usage far beyond what you're claiming. It's not true and it's unfortunate that Free Software folks push lies instead of acknowledging the drawbacks of the approach.
1
1
GPL heavily restricts usage within entirely open source software. The restrictions result in license incompatibilities. Permissive licenses don't have those kinds of license incompatibilities since they don't restrict usage of the code. GPL restrictions very regularly hurt FOSS.
2
You may think that the ends justify the means in this case but don't keep trying to pretend that it's not restricting usage including for open source software.
GPL is even incompatible with itself: GPLv2-only projects like Linux can't be mixed with GPLv3 along with other issues.
1
Projects with more permissive licenses also can't use code under more restrictive licenses without ending up with more restrictive licensing themselves. This completely applies within the set of GPL licenses. LGPL project can't use GPL code. GPL project can't use AGPL code, etc.
GPL creates different bubbles of restricted code that cannot be used elsewhere including in projects using other variants of the GPL due to license incompatibilities or just being more restrictive. It's a restrictive licensing controlling usage. That's the very clear reality.
1
If you won't acknowledge that, that's fine. I'll just add you to the ban list for our communities alongside other people unable to engage in honest discussions. Attempt by several people here to harm me and direct harassment towards me based on the thread will have consequences.
1
Show replies