This is what Tailwind should’ve done. It’s a shame to see hard work contribute countless millions of dollars to publicly traded companies and highly capitalized startups, and OSS creators not getting their due.
How I made $350K from an open-source JavaScript library using dual licensing
11–15 of 15 posts
Re: How I made $350K from an open-source JavaScript library using dual licensing
#12Thanks for sharing!
Re: How I made $350K from an open-source JavaScript library using dual licensing
#13One thing I mention to folks that seem to think AGPL "protects you" against a major corporation incorporating your product into a SaaS product: it mostly doesn't. It isn't written about often, but it's the reason many "open core" companies moved away from AGPL to protect their revenue from larger SaaS/IaaS/PaaS players from eating their lunch. Some writings are: - https://writing.kemitchell.com/2021/01/24/Reading-AGP…
It kinda does have that effect, because large companies are allergic to AGPL by policy, even if they otherwise have processes to get GPL software into use. The very companies that have the pocketbook to pay for your software, are also structurally incapable of using it as FOSS. Smaller ones that are more agile about how they incorporate it, have less willingness to pay for a different license.
Re: How I made $350K from an open-source JavaScript library using dual licensing
#14One thing I mention to folks that seem to think AGPL "protects you" against a major corporation incorporating your product into a SaaS product: it mostly doesn't. It isn't written about often, but it's the reason many "open core" companies moved away from AGPL to protect their revenue from larger SaaS/IaaS/PaaS players from eating their lunch. Some writings are: - https://writing.kemitchell.com/2021/01/24/Reading-AGP…
Law does not run on a CPU with certainty. There is risk analysis going on: there are many jurisdictions at play. When you are big enough, something that has fundamentally viral characteristics by design can have catastrophic impact even if reading of the license as linked would be almost certainly accepted as correct and likely. Therefore, especially for a company like Google that has a unified codebase, that treatment is justified. So goes for other big companies who would be at least wary of just taking AGPL.
Re: How I made $350K from an open-source JavaScript library using dual licensing
#15One thing I mention to folks that seem to think AGPL "protects you" against a major corporation incorporating your product into a SaaS product: it mostly doesn't. It isn't written about often, but it's the reason many "open core" companies moved away from AGPL to protect their revenue from larger SaaS/IaaS/PaaS players from eating their lunch. Some writings are: - https://writing.kemitchell.com/2021/01/24/Reading-AGP…
It kinda does have that effect, because large companies are allergic to AGPL by policy, even if they otherwise have processes to get GPL software into use. The very companies that have the pocketbook to pay for your software, are also structurally incapable of using it as FOSS. Smaller ones that are more agile about how they incorporate it, have less willingness to pay for a different license.
Sure, but there's a case I'm particularly aware of where one of the major cloud infrastructure providers was about to host a significant AGPL-licensed project without modifications because their lawyers had reviewed it and determined it would have been OK. The particular VC-backed open-core company then got word of it and changed their license off of AGPL. IYKYK