I can confirm what Danny says here. It's a shame the original article has such flaws in its argumentation, because at the core of it I think there are some goo

I can confirm what Danny says here. It's a shame the original article has such flaws in its argumentation, because at the core of it I think there are some good points. Notably, other people don't have to blindly follow Google's example and reasoning. In fact, as discussed here, there are good reasons not to. For one, because Google is so highly integrated (with Borg and its monorepo, not to mention custom approaches to security), it's harder to use AGPL software without risking linking. Most other users outside Google would just apt-get a package or the like. And of course the business risk to Google is large simply because of their scale. You can even disagree with Google's decision not to use AGPL, but they have openly explained their reasoning, and I think that adds to the discourse. Disclosure: I used to work at Google, and was fairly actively involved with open-source activities in different capacities while I was there. I am also on record as sharply criticizing Google when I believe that is warranted. This is just not one of those times.