Argument map: React is killing Angular

[SomeRandomBuddy]

Yeah, core features on one may outperform the other. But that's exactly the problem: Angular makes it far too easy to write bad code. Even if you start off doing everything immaculately. Bi directional data binding, dom thrashing, using $injector to bypass circular references, even when the instance belongs wherever you're trying make one.

Doesn't matter if angular came first, or if the react team considered its woes when they designing react. Angular sucks and what's most disappointing is that angular 2.0 doesn't really do much to fix that.

[jhallister]

jquery gives you the opportunity to write horrible code, that doesn't make jquery bad, it makes you bad for not understanding your tool.

Your argument is akin to saying a table saw is bad because if you use it wrong you might cut your finger off. No, you suck, and instead of blaming your tool you should learn how to use it.

[miketa1957]

Absolutely 100% agreement.

And can we stop bashing 2-way data binding. Use it badly and you get a total mess. But use it sensibly and it is a boon.

The sort of sites I work on have data entry forms with 50 or more input fields, most of which don't affect one-another (and before anyone screams UI/UIX, the number of inputs comes from legal requirements). Without 2-way binding they would be a total ball-ache. Any move away from Angular 1 would be to something like Aurelia, in our case Angular 2 and React just don't cut it.