> That said I've found Angular to be more than flexible enough to meet the needs of your typical CRUD apps
The OP says:
> Are there any use cases where Angular shines?
> * Building form-based "CRUD apps".
So I guess you and the OP pretty much agree.
It seems like the author is simply unhappy to be working in a framework not of his own design: "Create a metaframework based on angular, tailored SPECIFICALLY for your project needs and your team experience!" That's the one thing you shouldn't do if you want to reuse code between projects.
Would you really use DOM/virtual DOM templates to make a game? it makes little sense. I dont believe any "MV*" framework is suitable for games,even if the game is DOM based.
In a game,what you want is to make sure that at time T,the screen reflects the state of the game.Since you are manually pooling all states with a timer in order to render the game on screen,there is no need for databinding.
From you wrote, you implied that maybe you mostly make only typical CRUD apps, when you write that's where you've found Angular to be more than flexible enough?
So that could explain your different experiences/analyses? You both actually agree it's good for typical CRUD apps?
(some abstraction is fine, but a metaframework on top of a framework is just going too far.)