Re:Why Angular 2/4 Is Too Little, Too Late
by svdev on Sunday July 09, 2017 @09:04PM
(#14732693)
Also: Angular 2's Change Detection is a flaming tire fire of needless complexity.
Everyone benchmarks a Todo app and concludes that it has comparable perf to React. In practice, Angular 2's Change Detection makes apps incredibly slow.
Change Detection in a reasonably large app resembles a bucket of water, sloshing back and forth. Every template event and timer causes your Component tree to be re-rendered every time.
Because Angular doesn't encourage immutable data by default, and its ngFor directive optimizes for mutating data... Apps have a tremendous amount of trouble migrating to OnPush at a later time. It's a mine field riddled with gotchas and edge cases.
Angular2 lacks coherence. Or maybe its unifying theme is massive, needless complexity. It's not worth the trouble.
Everyone benchmarks a Todo app and concludes that it has comparable perf to React. In practice, Angular 2's Change Detection makes apps incredibly slow.
Change Detection in a reasonably large app resembles a bucket of water, sloshing back and forth. Every template event and timer causes your Component tree to be re-rendered every time.
Because Angular doesn't encourage immutable data by default, and its ngFor directive optimizes for mutating data... Apps have a tremendous amount of trouble migrating to OnPush at a later time. It's a mine field riddled with gotchas and edge cases.
Angular2 lacks coherence. Or maybe its unifying theme is massive, needless complexity. It's not worth the trouble.