The scope of the breaking changes matter more, and that story has yet to be told.
The scope of the breaking changes matter more, and that story has yet to be told.
When? Can you cite an example? Keep in mind that for most breaking changes React typically goes to a deprecation warning for the duration of a major release instead of hard-breaking changes, so in reality you have roughly double the time between truly breaking releases, generally speaking.
That is true about the deprecation, although some of the earmarked breaking changes have been quite painful too.
Hopefully the Angular team takes this route for planned breaking changes & apply engineering to ease compatibility.
The more I reflect, the more I see this as about poor expectation management and messaging from the Angular team than an actual story.