I mentioned “breaking changes” above. You may ask: how do TYPO3 developers keep the core state of the art by introducing new techniques and libraries while avoiding breaking changes when someone updates from one version to the next?
This is a companion discussion topic for the original entry at https://typo3.org/article/typo3-deprecation-policy