@DCMonkey: It seems that the post is indicating that it is better not to have the warnings than to have potentially poor implementations of the warnings, which might lead folks to think their code is fine when it isn't.
Great... I'm down with this, it makes sense.
Except one part: the compiler still accepts the switch! So now you think you have at least a mostly-working implementation of the warnings, but in reality there are no warnings!
Well, the post stated they would eventually remove the option, but I don't know if they ever did. In any case, I forgot that Apple uses the clang compiler front end these days so I don't think that post applies in this case after all.