I see no downsides: if my company ever grew to FAANG proportions, I'd be happy to pay a few million dollars (then pocket change) to open source projects I used.
I see no downsides: if my company ever grew to FAANG proportions, I'd be happy to pay a few million dollars (then pocket change) to open source projects I used.
More generally:
When a library is released under a strong copyleft licence like the GPL, then you are welcome to make use of it, but you are required to release your software under that same licence (i.e. to make it Free and Open Source), if you publicly release it. They do not prohibit you from making money, nor do they single out large corporations for special hostile treatment. Any licence that does, is unlikely to be considered a Free Software licence, or an Open Source licence.
(The AGPL licence goes even further than the GPL, and can apply even if you don't release your software. This is relevant for the software-as-a-service model.)
[0] https://www.reddit.com/r/programming/comments/803fx9/qt_comm...
As it is, we have Free software projects feeling cheated (understandably), and their only recourse is to change to more restrictive licences.
I don't imagine going AGPL would mean much for curl though, or other such applications. It's projects like MongoDB (no longer Free and Open Source software, according to Wikipedia at least) that we're normally thinking of when it comes to AGPL.