Here is an except of the FAQ of semver ''' If even the tiniest backwards incompatible changes to the public API require a major version bump, won’t I end up at

Here is an except of the FAQ of semver ''' If even the tiniest backwards incompatible changes to the public API require a major version bump, won’t I end up at version 42.0.0 very rapidly? This is a question of responsible development and foresight. Incompatible changes should not be introduced lightly to software that has a lot of dependent code. The cost that must be incurred to upgrade can be significant. Having to bump major versions to release incompatible changes means you’ll think through the impact of your changes, and evaluate the cost/benefit ratio involved. ''' Having a calendar of the breaking changes already planned like explain in the video seems dubious. And about Chrome, Chrome is an implementation not a spec, Angular is both an implementation and a spec. Do you really want a JavaScript 55 ?