[jheriko]

Any explanation for the downvotes? I concede the value of rapid application development, but objective-c itself doesn't provide this at all - rather the libraries like UIKit or Cocoa coupled with the Xcode development environment do this.

Objective-C is measurably bad for my code. I have reams of data to support this... and its all trivially reproducable.

[chrisdevereux]

I didn't downvote you, but you directed a lot of loosely-connected negative assertions at a single target without really backing any of them up.

Whatever you intended, it came across as a bit of a rant.

[jheriko]

when i mention the slowness of the message mechanism this is both by design of Objective-C (for runtime features) and very measurable. this is why, for example, NSArray becomes prohibitively slow when you want to iterate across 1000s of members.

Objective-C is nice, but its slow by design, and this rules it out in a concrete way for a lot of the work I've done.

Its sad when optimisation comes down to 'knowing better than the compiler' only because of language constraints. (even C has this problem with struct layout for example - its just prevalent when using Objective-C/Cocoa (Touch))