Not that many developers even try writing UB-free C (or C++), or want to. Almost always the UB works (might not be portable, might break with a future compiler.

Not that many developers even try writing UB-free C (or C++), or want to. Almost always the UB works (might not be portable, might break with a future compiler...) but im those cases they just debug the issues (or blame the compiler or don't update after all). I guess for moat projects that approach is actually economical.