3 ms·
I view the AGPL as a nonfree license; I think more permissive licenses are better, because I believe in software freedom. Companies are right to avoid the AGPL
by sneak 6y ago
I view the AGPL as a nonfree license; I think more permissive licenses are better, because I believe in software freedom. Companies are right to avoid the AGPL.
- LambdaComplex 6y agoYou believe in freedom for who, exactly? Freedom for the users of software? Or freedom for corporations who benefit from denying access to the source code of that software? The Free Software Foundation exists to protect the former at the expense of the latter.
- sneak 6y agoYou are dragging anti-corporate ideology into a very simple matter. Corporations are sometimes users, and individual people often benefit from denying access to the source code of software that is used to provide a service. Providing a service is fundamentally different from providing software.
- LambdaComplex 6y ago> individual people often benefit from denying access to the source code of software that is used to provide a service To the detriment of the users of that service--which are the people that the FSF aims to protect.
- sneak 6y agoThat's a very simplistic and, I think inaccurate view of the matter. My customers, for example, to whom I provide service, are not infringed upon in any way because I use private forks of GPL software in the provision of my services.
- LambdaComplex 6y ago> My customers, for example, to whom I provide service, are not infringed upon in any way The issue is that I—and, more importantly, your customers—must simply take your word for it, since we're unable to confirm or deny it for ourselves if you don't make the source available. When dealing with large corporations, taking such statements at face value is pretty foolish.
- throwaway2037 6y agoThis is an interesting point. The original question was what if my database was AGPL, and it's source code was modified. If this database was used as part of a public (cloud-based) web-app, how could end users ever know there is a custom database? You are right: It seems likely that less ethical orgs would just lie and say they use the database unmodified. Thus avoiding the obligation to publish their database modifications as required by AGPL.
- CRConrad 6y agoThey will be when you go out of business and disappear, and they can't compile that same service to run on their own replacement server because you've withheld the source to your modification. You might not want to admit to yourself that your business model is based on infringing on the freedoms of these users of GPL software, but that's exactly what it is.
- lmm 6y agoThere's nothing anti-corporate about it. The AGPL is motivated by the same thing that motivated the original GPL: making sure that users have access to fix bugs in the software they're using, like in the printer driver anecdote. The AGPL doesn't require you to provide the source for software that you're using to provide a service - only the source for software where the software is the service. A bug in software I use is equally annoying when I'm using that software over a network connection as it is when I'm using it on my local machine.
- rocqua 6y agoWhat about freedom for developers? It seems to me that, to defend users against corporations, the FSF as a side effect is attempting to take a whole lot of freedom away from developers who share the ideals of the FSF. (That is, any developers who publish under MIT / BSD like licenses)
- ternaryoperator 6y ago"Companies are right to avoid the AGPL" This was never an issue until Google was pinched on it five or six years ago and started a massive campaign to get the OSS movement to disfavor the AGPL. Google uses tons of GPL software that they don't pay for (Linux, Java, etc.) but once it became exterior-facing and the license applied to their software, then rather than pay to license the software, the world's fifth most valuable company decided they'd rather stiff the developers by a campaign to convince other companies of what you just posted.
- sneak 6y ago> Google uses tons of GPL software that they don't pay for (Linux, Java, etc.) but once it became exterior-facing and the license applied to their software, then rather than pay to license the software, the world's fifth most valuable company decided they'd rather stiff the developers by a campaign to convince other companies of what you just posted. The free in free software is often cited as being "free as in freedom", but it's important to remember that it's also and simultaneously "free as in beer". Google, along with everyone else, uses tons of GPL software that they don't pay for - because the point of free software is that you're free to use it. They're not "stiff[ing] the developers" as you claim, because the software is available for all to use for free. You can't have it both ways: either you're free to use the software for any purpose, or by using the software you owe somebody something. Pick one. I choose the former.
- ternaryoperator 6y agoWhy do I have to pick one? It's not a binary thing. Why can't developers say it's free to use under these circumstances, but not under others? Isn't that precisely the freedom you are otherwise championing? The only reason Google opposes the AGPL is financial. Read their explanations. So, while you're right that Google is not 'stiffing' the developers whose software they're using, by their campaign against the one license that can be used by developers to make money, they are making the OSS world weaker--especially for programmers from developing countries who don't have the luxury of large blocks of time to write software on the side unless they can benefit from a license like the AGPL.