You are right that AGPL is easy if you can just run it as-is. The real problems start with libraries. If I link an AGPL PDF-generating library with my monolith service which runs financial reports over my business, what happens? Do I need to now publish my SQL queries that access sensitively named tables? Maybe that reveals new secret projects we're working on, or perhaps security incident mitigations underway.
Sure, there are countless ways to architect my way out of those problems, but what if I don't have the resources to do that right now?
The small obligation becomes a large burden pretty quickly.
(The real solution to the above problems is to pay for the corporate license that removes the AGPL obligation, but that assumes you can afford to do so)
AGPL is fundamentally scary to lawyers and management because they're afraid someone will sink the ship. Sure it's mostly FUD, but there are some serious valid concerns.
No one uses AGPL for libraries, except maybe by mistake. LGPL is used for this purpose.
>Do I need to now publish my SQL queries that access sensitively named tables?
No. The FAQ from GNU makes how this works pretty clear:
https://www.gnu.org/licenses/gpl-faq.html#AGPLv3InteractingR...
The AGPL is not viral in the sense that all client software accessing an AGPL-licensed service are required to use the AGPL, but rather, such clients are entitled to the source of that service. It puts no obligations whatsoever on client software.
https://www.gnu.org/licenses/gpl-faq.html#AGPLv3InteractingR...
Maybe you should actually read up on the AGPL license before you make assumptions about it? It seems like you don't really understand it.
This isn't my experience at all. Here's an example:
https://github.com/unidoc/unipdf/blob/master/LICENSE.md
> The AGPL is not viral in the sense that all client software accessing an AGPL-licensed service are required to use the AGPL, but rather, such clients are entitled to the source of that service. It puts no obligations whatsoever on client software.
This depends on what your "client" is. If you're making library calls, lawyers get uncomfortable.
> Maybe you should actually read up on the AGPL license before you make assumptions about it? It seems like you don't really understand it.
I understand it quite well, and I even use it myself! There are just problems associated with it that most proponents gloss over.
Ah, in this case, this software is designed to maximize conversions to the paid commercial license, so they deliberately use the AGPL in a way which makes it inconvenient for your internal use. This is not common in software which does not have an alternative commercial license. I don't really appreciate this model because it is disrespectful of the copyright of third-party contributions.
I actually do. If I write a library, I definitely don't want people to put a web UI on top of it and get away without any obligations, like so many people do for e.g. website that are just ffmpeg frontends.
Just wanted to mention that I believe AGPL is sometimes considered with a dual-license scheme in the hope that enterprises buy the commercial license, or to avoid a situation where a commercial third party benefits from a piece of software disproportionally, or to the detriment of the project's funding (such as providing pure hosting), whether contributions are upstreamed or not. Not being able to express clearly what you're after - cash or code - makes AGPL suboptimal. It's a reality that software without funding and maintenance only goes into bitrot mode, so why not come out straight and sell potential customers maintenance and support? Clearly, the software licensing universe needs additional considerations today compared to the time when Affero/AGPL was conceived.
In actual fact, being compliant with AGPL software is extremely easy. Nothing at all is expected of you if you just ship it into production as-is. And if you modify it, the only obligation is to send the modifications upstream as patches. That's it. Surely any company is capable of completing such a trivial feat.