> Because it solves real world business problems. Some people need to build large systems in a SPA framework
This sounds...circular. "AngularJS is a framework for building large SPA framework systems solves the real world business problem that business need to build SPA framework systems."
Frameworks don't solve business problems, practically by definition; they're potentially the common factor across software systems that solves part of the technical problems of developing an application.
That's assuming a framework is any good, of course, but we're talking about Angular, so by all means: tell us what development problems Angular solves for you.
And if I were defending Angular, I don't know that I'd invoke the problems of fashionability and the bleeding-edge of change, because it's hardly insulated.
I think you're wrong, but only because you went in the wrong direction. In my experience Angular is best for the "I don't care how, I just need it done" crowd. The architecture, data model, routing setup, etc are all defined for you. However I've found React/Vue/Ember are better for "I need to create a complex system with a long shelf-life that will be touched by many people".
Not everyone is building a cheap hackathon twitter clone in their spare time.
For some of us the JS framework is solving business problems, not hobby JS side projects using the latest hip JS frameworks.