Originally Posted by
MK27
Fair enough, except that I imagine what you mean by "insecure" is that they are prone to be if not used properly. So if the "security improvement" is like, commands that do not allow buffer overflows no matter how dumb the programmer, that is asking to excuse dumb programmers. It is C. It is low level. You do your own memory management. That is what it is for. Otherwise, you might as well use another language.
So that whole spiel sounds a great cover story to me. After all, they cannot actually say, "Oh, we are doing this in the interest of intentional incompatibility on the recommendation of the business division", which is more likely.