>> The fear is that a company could be forced into open-sourcing software that was not intended to be open source. > wikipedia says agpl was brought in 2002. s

>> The fear is that a company could be forced into open-sourcing software that was not intended to be open source. > wikipedia says agpl was brought in 2002. so around 21 years of people using this license and no one knows clearly what it does? The fear referenced here isn't about what the license does. The fear are the unknowns about how it will affect business operations in the future after building a business around a piece of code with that licensing obligation attached to it. > you can use unmodified AGPL code alongside proprietary code, all you have to do is put the license file up there. You cannot. AGPL only has one linking exception, and it is for code licensed with GPL.