I do not have much experience with Angular, however, I feel the arguments over different frameworks depend a lot on the specific nature of your app. two-way da

I do not have much experience with Angular, however, I feel the arguments over different frameworks depend a lot on the specific nature of your app. two-way databinding is perfectly fine and really helpful for a lot of apps. However, it will screw you for certain use cases. In my opinion, it really boils down to how much global interaction you have in your app. If you simply render a lot of models that can only be changed trough the view, then I don't really see a reason for a Flux like architecture. Two-way databinding is perfectly fine there. (React vs whatever then boils down to performance vs toolset) If you do a lot of graphical stuff that allows for heavy interaction, filtering and other kinds of stuff, I believe that two-way databinding will be your downfall. You need to clearly and explicitly map out on how data flows through your app. That is the time where an architecture like Flux shines. So ask yourself this question: "How often can a user do something in your app, and a lot of Views need to rerender?" If the answer is "often", then you should consider something like Flux. If not, Angluar might be a better fit, especially if you already know it.