3 ms·

It's very understandable that developers would want to stay away from C and stick to the nice OO features of Obj-C. That's probably why the language was uncere

• mpweiher 8y ago
  > it's hard and unpleasant to reconcile these two worlds Couldn't disagree more. For the C types that tend to occur in bulk processing (bytes, integers, floating point numbers), C is great and Objective-C is...er...not so great ;-) On the other hand, Objective-C is fantastic for hooking modules of these C-based data crunching methods together. > Btw, what is the perf problem then? Refcounting, boxing? Refcounting can be a problem, yes, but pre-ARC it was both much less so and pretty easy to avoid if you noticed it. Also the fact that NSObject and subclasses had no inline refcount, so went to an external hash-table for refcounting if it ever exceeded 1 (1 was implied by the object being alive). More in the other answer, there isn't really "the" perf problem, there are various problematic implementations and habits promulgated by Apple, often without any good reasons.