4 ms·
Thanks for the explanation! Does anyone actually release code due to this license (which they wouldn't have released otherwise)? I'd imagine generally if a comm
by taneq 8y ago
Thanks for the explanation! Does anyone actually release code due to this license (which they wouldn't have released otherwise)? I'd imagine generally if a commercial developer saw a license like that they would just choose not to use the AGPL code. I know I won't use any code or libraries which place these sorts of obligations on me as a developer, unless it's in a product that I was planning to release the source of anyway.
- rfrey 8y agoIf a commercial developer saw a license like that... they could pay for a commercial licence. Presumably a commercial developer thinks software is worth paying for.
- ternaryoperator 8y ago> if a commercial developer saw a license like that they would just choose not to use the AGPL code. Except for the server bit, the restriction being described is called copyleft. And it appears in all GPL licenses, except LGPL. Some of the major OSS in use today is released under it: Linux, MySQL and MariaDB, VLC, and of course all the FSF software, such as GCC.