It has been discussed on HN before : https://news.ycombinator.com/item?id=7719957
Some good comments there, worth checking out. Personally, I think the message loop architecture proved very good in Windows when processors were slow and had only 1 core and it is at least worth giving it a try in web development.
Hence my question. I feel like for some apps I don't need 60% of what Angular has to offer (routing, controllers, modules etc.) I would be satisfied with just directives. Which are probably the part of Angular I like the least.
For SPAs I see no other alternative to Angular currently. In instances where I need heavy JS only on some pages, I'm not sure.
You could then incrementally add logic client-side to improve performance, if that's necessary (if the state object becomes too large, for example).
<my-svg-shape my-directive-that-mutate-svg-props />
The big weakness of Angular is server side rendering,which involves heavy solutions like phantomjs,while you can render react components on the server.
Angular is not very good at rendering/managing svg either,that's a fact.
I would argue maintaining pure html templates is not that hard.
But frankly Angular solves so many problems these are minor issues.Writing complex lob applications is so easy with Angular I wouldnt want to use anything else.
The only case i'd switch back to backbone+react/vue/ractive and jquery is when i'm writing interactive experiences that are not CRUD apps.
So no,dont switch to React for the sake of switching especially since AngularJS just works. I mean people dont even bother learning javascript,they learn AngularJS ...