But you can still run into strange race conditions where the browser displays stale data depending on if some other unrelated code has caused a digest update to run after the buggy code or not.

The advantage of ngOnChanges() is that we get all the changes at once if the component has several @Input()s. However, if we have a single @Input() a setter is probably the better approach.

how it uses zones