Finally, Java may suck as a language but so does Obj-C. Looking at O-C code is like looking into a code museum. So spare me.

Now for some, including me, Objective-C *is* a lot easier to read and a lot cleaner. You can more easily see nesting thanks to the square brackets, you have interspersed arguments which makes methods far more self documenting and you can do more in less code thanks to the dynamic dispatch.

The issue is, you are complaining about Obj-C being “slow” because of dynamic dispatch. I can show you 100s of Obj-C apps that run perfectly fine despite dynamic dispatch and 100s of Java apps that run slow even with the static method calling. Hell, have you tried an Android phone and iPhone side by side? It is ridiculous how slow the Android is in comparison at times, yet it is selling reasonably well.

The fact is that these things are largely irrelevant and the majority of performance problems come from APIs or just bad code. The largely insignificant runtime cost of dynamic dispatch is more than made up for by the very significant savings in development time that a dynamic language affords you. Users don't care about invisible speed issues, they care about real speed issues. Developers don't care about getting every last little bit out of their code, they care about writing less code, faster. This is why we write in Objective-C, C, Ruby, Python, C# and even Java instead of Assembly. About the only time you *really* need to drop down to C and where Obj-C is “slow” is when you need realtime processing, such as audio, in which case almost anything bar C is likely to be too slow and sometimes C itself can be.

Separate from that, I think you misunderstand the amount of function calls done using the objc_msgSend system in a real application.