First and foremost, I don't enjoy using it – I find the language much more difficult to read and parse than ObjC, especially with if-let variable assignment in loops and switch statements (which is chaotically overused in Apple's body of sample code, like for ARKit). Steve Troughton-Smith: There are a variety of reasons why I avoid Swift. Sponsor Hacking with Swift and reach the world's largest Swift community! What are the main reasons holding you back from switching to Swift as your primary language? SPONSORED From March 20th to 26th, you can join a FREE crash course for mid/senior iOS devs who want to achieve an expert level of technical and practical skills – it’s the fast track to being a complete senior developer! Note: Views expressed here are personal and may not represent the views of their employers people are listed in the order they responded some answers were edited for length.

I got in touch with some Objective-C developers to ask what’s holding them back, whether they feel Objective-C development has become stigmatized, and more – here’s what they had to say… Yes, it might occasionally get dusted off for a slide or two at WWDC, but the majority of conference talks worldwide are in Swift, Apple is pushing Swift hard in the education space, and major language features come to Swift first.īut if you’re still using Objective-C, you’re not alone – many other developers still prefer Objective-C to Swift, and with good reasons. Objective-C – once the rising star of the app development world – has started to become a second-class citizen in the Apple ecosystem. But those times are gone: Swift has been with us for over three years now, and has largely pushed its older sibling from the limelight. For several years after the iOS SDK was announced, developers were flocking to Objective-C as they sought to get their slice of the app development gold rush.

Xcode objective c