Earlier quoted context omitted.
It's about effective advocacy. Stallman can think or do whatever he wants, but he is not and has never been an effective advocate. And from an advocacy position, ideological purity almost never works. An advocacy organisation like the FSF should be pragmatically "climbing the ladder" one step at a time, not insisting on an instantaneous revolution. You might as well advocate for the moon to be painted blue: it's just…
Unfortunately I don't even believe Stallman is as ideologically pure as people like too believe he is. I think he is much more attached to his own ideas and realisations than he is to the overarching idea of software freedom. And to support that argument I bring three anecdotes. 1. He is much more attached to his own creation, the GPL, as a tool for driving software freedom and as a "hack" on top of copyright. As suc…
2. Nobody stops anybody from creating new licenses, in fact many many projects tried to do just that (MPL etc). Most of them fail simply because you cannot have your cake and eat it too, you either allow some things or you don't. You either require source code for programs users interact with on the network, or you don't; I'm not sure what middle ground is there to find. If you want to release certain parts of a website but not others, you can do it already in many areas - any SPA client-side code can be covered by GPL 3, for example. AGPL in many ways was a proto-GPL3, and it's to the FSF's credit that they didn't drop it, but actually updated it when v3 came about. They even try to explain the differences with dedicated documentation [0].
[0] https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-t...