GPL carries no restrictions if you don't distribute the software.

The AGPL on the other hand, was a huge mistake, IMO.

The AGPL was the first step in addressing a critical need to protect the users' right to run the software they use, the SSPL just continues that, as many services wouldn't be runnable without the support code around them.

I hear what you're saying, but those whose mission is to encourage open source software don't call the SSPL anything but a source-available, proprietary software license. Like literally the organization that defined what "open source software" is.

While you may disagree, you aren't going to convince me to take your word over theirs, especially when I have come to the same conclusions they did on my own.

On a moral principle, AGPL levels the playing field fairly much like the GPL license, just the terms of distribution are updated for an age of software as a service. No one is exempted to the rules in AGPL like SSPL - it is intentionally viral, even if you'd dislike using it in many of your projects (though I think it's fair to say lawyers don't like the ambiguity of the language).

Just like some projects are best under LGPL instead of GPL, AGPL has its place in the toolkit of free software licensing.