I am trying to understand the exact use of ngOnInit with regards to component constructor and ngOnChanges methods. The only argument I can find for using ngOnInit instead of constructor as a place for initializing Component state, is that Component inputs are not yet available in the constructor. However, if ngOnInit is not called when Inputs change during navigation across which a given component is still visible and thus not destroyed and recreated, ngOnChanges seems to be a much safer place to do any init logic that depends on component inputs. Then, ngOnInit seems useless to me, since it cannot do anything we cant already achieve with constructor and ngOnChanges.
Do you know any further reasons?

Thank you very much!

This section is useless since so many questions are theoretical and not really tied to a practical problem…