&gt;  Just fine in the sense that it&#x27;s the dominant language on iOS, and iOS sets the bar, IMO, for snappy experiences on modern platforms.<p>&gt; Stuff implemented in java and javascript, not so much.<p>I agree with the data but not the conclusion. iOS&#x27; performance is great in spite of using Objective-C as its language, not because of it.<p>The only performance-related features that Objective-C brings to the table are (a) being able to piggyback on the optimizations implemented in popular open source C++ compilers; (b) being compatible with C, so you can easily inline C into Objective-C when Objective-C&#x27;s slow performance bites you; (c) not requiring tracing garbage collection. When you&#x27;re actually in heavy Objective-C land with method calls in tight loops, performance is pretty bad, both because message sending is slow and because methods can&#x27;t be devirtualized. Apple knows this, and they&#x27;ve basically reached the limit of what they can do without incompatible changes to the Objective-C semantics. Hence the performance-related design decisions in Swift.<p>(As for UIScrollView&#x2F;UITableView, I agree that they&#x27;re very fast relative to Android or current Web browsers for example. I know the reasons for this and they have nothing to do with the implementation language. Algorithmic and engineering concerns often trump programming language performance.)