4 ms·
Because it infects code even if you don't modify it. You could just be using an API of an AGPL service, and it will hit your code. Its universally banned no
by adrr 3y ago
Because it infects code even if you don't modify it. You could just be using an API of an AGPL service, and it will hit your code. Its universally banned not just startups. I don't know of any organizations that allow it in their code base. If you want people to use your code, don't AGPL it.
Here's google's policy on it.
https://opensource.google/documentation/reference/using/agpl-policy#:~:text=Because%20Google's%20core%20products%20are,software%20to%20doubly%2Densure%20that https://opensource.google/documentation/reference/using/agpl...
- josephcsible 3y ago> Because it infects code even if you don't modify it. No it doesn't. The extra section of the AGPL that the GPL doesn't have explicitly says it only applies if you do modify it. > Its universally banned not just startups. You linked me to the rule that it's banned at Google, but still not to the source of any rule that it's banned at any startups.
- yencabulator 3y agoHow about this: There are AGPL software vendors who think making HTTP requests to their AGPL software forces you to license the client as AGPL too. To avoid their lawsuits, companies forbid internal use of AGPL software.
- JohnL4 3y ago7-day-old comment, but the company I work for (not a startup) flat-out bans creating a dependency on AGPL code.