>Anki unfortunately jumped the AGPL shark recently, making the code dangerous to have around.
Seriously?
Do you sometimes sneeze and, in the process, integrate your projects with external code (that isn't even packaged as a library) and push it out to users in one fell swoop?
It's far more "dangerous" to have any proprietary software "around" -- if you somehow violate that license, you'll face a lot worse consequences than if you violate the AGPL.
The problem is that the AGPL taints the output of the software, not the software itself. I'm fine with the GPL, that's well-understood, well-deployed, and well-tested in court. The AGPL? Nobody knows.
That's entirely untrue. There's no way to even do that, short of having a copyrighted asset included in every output (but that could be trivially changed and has nothing to do with the license).
I also fail to see how such a thing, even if it were true, would make the AGPL "dangerous to have around."
Seriously?
Do you sometimes sneeze and, in the process, integrate your projects with external code (that isn't even packaged as a library) and push it out to users in one fell swoop?
It's far more "dangerous" to have any proprietary software "around" -- if you somehow violate that license, you'll face a lot worse consequences than if you violate the AGPL.