My biggest complaints about angular aren&#x27;t really the dirty checking system that it uses (though one of them is a side effect).<p>My biggest complaint is the weird dependency injection system that makes it difficult to track down where something comes from.  It&#x27;s better in 2, but still not as straight forward as React, where your child components are simply import&#x2F;require statements that you can follow through to either an installed npm module, or a relative path.  I try to avoid DI in JS wherever possible, it&#x27;s almost never needed, and there are almost always simpler ways.<p>My second largest complaint on angular, is that I find that the way it handles state (though many are moving to a more react-like approach) leads to anything outside of the &quot;angular way&quot; being <i>very</i> complicated to work around.  The fact that $scope.apply() is a thing kind of sums it up pretty nicely.<p>For most applications (we&#x27;re not all building facebook level interactions), either comparison approach is not a performance issue in practice.  What I do find is the flux&#x2F;react way tends to have a bit more cognitive overhead to get started with, but additional features add less additional complexity than with angular.