Maybe you're right. I thought it is understood why pro-gplv3 people like the licence.
Just to elaborate then, I personally want my software to use gplv3 because I side with the ideological/ethical aspects of free software. I want to support projects/teams/orgs that build this future. An mit licence would allow a company to capitalise on the community's effort withought giving nothing back. Or even worse, make modifications and deliver closed source blobs to users. I personally do not like that. Thus, I wouldn't support/use this library.
To be clear, I am not running 100% gpl software atm, but I see it as a journey going there, slowly transitioning.
That isn't what it means but the problem with it is that it has extra knock on effects.
There is a reason GPL v2 was incredibly popular and GPLv3 basically killed all momentum and it wasn't because GPLv3 was better. At least not from a business point of view.
And that, at its core, is the issue. In a world where the only licence is GPLv3... it works. But in a world where people can choose other licenses - it won't be the choice of most.
It's a shame because I love the GPLv2 but I'll never use GPLv3 and honestly it's just less hassle to chose MIT for most companies.
No I don't ... because the GNU GPLv3 guarantees, more than any other license, user freedom. The only other license that might guarantee more user freedom in this case is the the GNU AGPLv3. Sorry, but the MIT license does little more than protect a developer from being liable, it does almost nothing to promote freedom.
No, the GPLv3 grants the user more freedoms than a license like MIT - they can demand the source from someone who has provided them the binary. It grants potential distributors fewer freedoms - they must provide sources and cannot distribute under incompatible licenses.
I don't really see any malicious intent here. I've started avoiding the GPLv3 myself just because it makes code that I publish harder for people to take advantage of. What's the point of me writing some code if it's only going to sit on Github, as if it were ment for some sort of museum?
Apache and MIT Licenses are generally my goto these days.
I assume the author chose this licence because it reflected his wish for the user's freedoms to run, study, share and modify the software to be guaranteed. He probably doesn't want a permissive licence.
It's not FUD, and GPLv3 is not clearly a superior license. It may surprise you to learn that different people value different things and have different opinions, and so want different licenses. GPLv3 is really a pretty extreme license that imposes a lot of restrictions that a lot of people simply don't want. If GPLv3 does what you want, by all means use it, but don't denigrate the choices other people make.
Before I could give more of a look into it, the license jumped at me. What's the idea behind using GPLv3? Who do you want to enable to use this, versus whom are you trying to prevent from using this?
Most businesses don't want to touch GPL code, particularly GPL v3. By licensing it as GPL v3 the team is basically saying "no one but students and hobby programmers will ever touch this code."
Just to elaborate then, I personally want my software to use gplv3 because I side with the ideological/ethical aspects of free software. I want to support projects/teams/orgs that build this future. An mit licence would allow a company to capitalise on the community's effort withought giving nothing back. Or even worse, make modifications and deliver closed source blobs to users. I personally do not like that. Thus, I wouldn't support/use this library.
To be clear, I am not running 100% gpl software atm, but I see it as a journey going there, slowly transitioning.
reply