> So if you never want megacorps or anyone who runs a business to ever use your code, choose AGPL.
Not "anyone who runs a business" but "any business that uses your software to provide a proprietary network service".
That is the whole point of the AGPL!
Google's reasoning in your link is pretty clear that the problem is that they are a provider of network services. Most non tech businesses wold be completely unaffected by these issues and have no reason to care.
The problem is that the language is vague enough and untested enough a lot of places, including non-technical ones, can be wary of being the test case.
What would it take to test it in court? Plenty of projects choose AGPL for whatever philosophical / moral reasons, perhaps even out of fear of competition. Is it just that it's "radioactive" enough to scare away anyone who'd consider it actually interesting?
I imagine it could take some minor contributor deciding they don't like what you do and taking extreme interpretation of AGPL including trying to insist everything that talks over network to it is derivative work, vs interpretation of yours (let's say you're not modifying an AGPL project at all, just running it vanilla, and it's part of some bigger offering, and your lawyers said it's not crucial enough for the bigger offering to be considered derivative)
As far as many people are concerned, AGPL is vague enough it would end up in court, so the question becomes "do I want to have this sword of Damocles of unnecessary complications and upsets?"
Not "anyone who runs a business" but "any business that uses your software to provide a proprietary network service".
That is the whole point of the AGPL!
Google's reasoning in your link is pretty clear that the problem is that they are a provider of network services. Most non tech businesses wold be completely unaffected by these issues and have no reason to care.