![]() ![]() I'm fully of the belief that just because Apple builds something and says it's the way forward doesn't mean it's the right choiceĪnecdotally I had heard, for the first few years, that Apple was as divided on Swift as anybody - Apple is, of course, a massive body of ObjC developers and Swift was as much a surprise for many of them as it was for us. I lose nothing from waiting until Swift is 'ready', and I gain all the benefits of Objective-C in the meantime. I understand why that is the case (ABI stability, etc), but if Apple's not using it for everything I don't see why I need to be beta-testing on their behalf. I'm not yet convinced of Apple's level of participation in the language - four years on, Swift is not used for important pieces of iOS, OS or frameworks (I maintain a running list of Swift apps from Apple on Twitter, and macOS is definitely less shy about adopting it for new features than iOS). I am no newcomer to different languages, having written things for all kinds of platforms, and Swift is definitely at the extreme low end of the legibility spectrum for me. 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? In just four days, learn how to create your own Twitter using Stream Chat, Algolia, 100ms, Mux, and RevenueCat. SPONSORED Build a functional Twitter clone using APIs and SwiftUI with Stream's 7-part tutorial series. 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. ![]()
0 Comments
Leave a Reply. |