It should be noted that Objective-C code is presumably a lot less prone to memory safety issues than C code on average, especially since Apple introduced Automa

It should be noted that Objective-C code is presumably a lot less prone to memory safety issues than C code on average, especially since Apple introduced Automatic Reference Counting (ARC). For example: • Use-after-frees are avoided by ARC • Null pointer dereferences are usually safe (sending a message to nil returns nil) • Objective-C has a great standard library (Foundation) with safe collections among many other things; most of C's dangerous parts are easily avoided in idiomatic Objective-C code that isn't performance-critical But a good part of Apple's Objective-C code is probably there for implementing the underlying runtime, and that's difficult to get right.