4 ms·
FWIW, the Angular team is aware that this is a pain point. There were several talks at NG-Conf a few weeks ago that referenced replacing or removing zone.js-pow
by jamesgeck0 7y ago
FWIW, the Angular team is aware that this is a pain point. There were several talks at NG-Conf a few weeks ago that referenced replacing or removing zone.js-powered change detection for increased performance and/or smaller build sizes. They're trying to avoid another Angular 2 situation though, so it may take a while for a backwards compatible solution to surface as the default.
- nicoburns 7y agoThis is precisely what I don't like about Angular. That there is all this stuff. And I have to care about what it is doing under the hood (and this is complicated and not especially well documented). In React if I have performance issues, then it's pretty easy to work out what's causing them.
- jamesgeck0 7y agoYou can largely ignore what Angular is doing under the hood, tbh. If you're having performance issues, the answer is often related to change detection (aka, Zone.js).
- nicoburns 7y ago> If you're having performance issues, the answer is often related to change detection (aka, Zone.js). This is part of Angular really. At least it's not optional to use it. Change detection issues are not fun to debug!
- jamesgeck0 7y ago> At least it's not optional to use it. Zone.js is optional, although it is on by default. It's considered best practice to remove it when building standalone components with Angular Elements.