My misalignment with Apple's love affair with Swift
As someone with a significant amount of experience in both ObjC and Swift (4+ full-time years in each), I don&#x27;t agree with this article. Yes, Swift isn&#x27;t perfect, it has its flaws. Totally agree there. It&#x27;s not perfectly integrated with Cocoa either, as the author mentions.<p>However, to say that Swift is a regression over Objective C seems very short sighted to me. Can you imagine if Apple continued with Objective-C? There would be no way to reverse decade old decisions that simply aren&#x27;t the right decision anymore. Every new feature would need to be built on top of code from 1984. Swift was very future focused from the get go, and is a bid to ensure that developing for Apple devices in 2025 is not an archaic mess.<p>Like anything new, it&#x27;s not perfect at first. That is the world we live in now. However, Swift is getting incrementally better at a very good pace. There are some reasons left to prefer Objective-C right now, but I&#x27;m sure that in a few years these reasons will be far fewer.<p>My own opinion is that I&#x27;m much more productive writing Swift, after spending a similar amount of time with each language. If you think the same is true of Objective-C, then that&#x27;s great - there are certainly still some upsides to developing with Objective-C. However, to say that Swift is a mistake is something that I can&#x27;t reason with, since it&#x27;s one of Apple&#x27;s most forward thinking decisions to date.