I think so, but I tend to think of it as not the AGPL's fault, exactly. That is, the GPL was a product of its time: it's very concerned with the details of writing non-networked C code. It pre-dates the web! It was impossible to forsee these kinds of changes, and it just so happens that it was not really prepared for them. The AGPL was an attempt to plug that hole, but it was too little, too late.
Yea, I don't think it's AGPL's fault. I think people became complacent with the landscape of GPL and what that meant for production applications but when GNU came around and tried to make it all apply uniformly (right after dot-com) OSI had already gained enough traction that a full GPL looked "weird" and turned into more of a signal that you didn't want anyone to use your code. That and Google et. al. banned it as it obviously threatened its model that some might see as abusing GPL.
I think so, but I tend to think of it as not the AGPL's fault, exactly. That is, the GPL was a product of its time: it's very concerned with the details of writing non-networked C code. It pre-dates the web! It was impossible to forsee these kinds of changes, and it just so happens that it was not really prepared for them. The AGPL was an attempt to plug that hole, but it was too little, too late.