Not only has the standards comitte not done anything serious about preventing bounds overflows, they made it optional.
Sizes still aren't guaranteed to be correct for the string/buffer.
No portable C code can rely on its presence.
What I am in favor is Microsoft pushing C aside.
C++ provides safer constructs and if one wants to keep on doing unsafe C style coding, it is still there.
Not only has the standards comitte not done anything serious about preventing bounds overflows, they made it optional.
Sizes still aren't guaranteed to be correct for the string/buffer.
No portable C code can rely on its presence.