Replies that are other Swift is probably your absolute affordable papers sign in best guess for basic purposes currently. Nevertheless, you can still find likely to be times when #039 & it;s useful to have quite finegrained control over things, where stage a working familiarity with C and Objective-C you may endure in stead that is excellent. For example, let's claim you implement a red-black tree in Swift along with your app’s remainder. After profiling, you see that #039 & there;s a lot of time being spent after you', even in this point; it was enhanced by ve towards the finest of one’s capacity. At this point, it might be worth re-implementing it in Objective C: the software exported for your Fast API is likely to be similar (usually if you're returning tuples, etcen you can subclass it in Swift to re-include that operation), and you'll manage to definitely tighten down the rule to some amount that probably wouldn't be as straightforward in Speedy. I do believe Greg Parker explained it best when he said that Objective-C would currently be a type of ' Object-Oriented #039 & Assemblage; vocabulary. Not needed very often, but important for anyone small instances (Objective C and Instant message-passing is implemented in fresh assembly code).