They're right, but they're presenting it in a way as if the toxicity of AGPL is the actual truth, and not just the opinion of greedy corporations.
replyBeing toxic to greedy corporations but beneficial to everyone else is the point of the GPL licenses.
But it’s not only toxic to the greedy corporations but all the others as well, hence
replyWhy is it toxic for me to need to push my code to a git repo if I start using it in my services, if I'm not trying to act as a for-profit corporation?
replyHow so? You might be thinking of SSPL.
replySeems like the path is to use LLMs to launder code from VC funded efforts and their public codebases into codebases with a copyleft license. Otherwise you have to wait for the rug pull before taking action (Terraform and Vault->OpenTofu and OpenBao). It is fair use to train and create derivative works after all, as courts have ruled so far.
replyYou can just take someone else's permissively licensed code and relicense it AGPL, or even proprietary if you want to. Corporations want it proprietary but the same trick works for copyleft.
replyFor bonus points make sure your fork has better SEO than the original, so when someone who heard it's permissive embeds it in a proprietary product, you can sue them.
Was assuming worse case scenario from a licensing compatibility and copyright perspective.
reply