It is not the particular situation people are upset about (well, at least me). It is the reasoning, especially in the context of &quot;you shall not write undefined behavior according to the standard even if it should makes sens given the computer you are actually programming&quot; that is usually sent on us regular programmer by compiler authors... :&#x2F;<p>Yet they do exactly the same thing, and pretty much casually. And I actually don&#x27;t really blame them for doing it. Everybody makes mistakes. But I blame them for the double standard, the risks, and the attitude. The problem in the first place: engineering is also about mitigating the fact that mistakes will happen, often mitigating even the mistake of others, and the modern approach in regard with undefined behavior does not help and is even ultra-hurtful for that. I don&#x27;t see how stability will emerge with that kind of thought process.