4 ms·
Mirrors how I felt about iOS development through the 2010s for the same reasons, with the exception that the language, Objective-C, was likely holding it back i
by samtheprogram 4y ago
Mirrors how I felt about iOS development through the 2010s for the same reasons, with the exception that the language, Objective-C, was likely holding it back in a way Visual Basic did not.
I’ll always have an affinity for Objective-C but obviously a C-based language with pointers everywhere came with a learning curve. Swift could have solved this but the APIs were not stable at the time (I used it around 2.1) and the compiler sometimes would choke with somewhat hard to diagnose errors. It seems Interface Builder and Storyboards are getting replaced by SwiftUI these days (inspired by Elm/React).
- Cthulhu_ 4y agoI think I have the same experience; it was definitely a step up from what I've done most of my career (webapps), mainly because it was all integrated and unified. I didn't mind objective-C, we did run into tons of crashes due to e.g. http requests coming in for screens that were gone already, but that was a matter of sticking to some stricter coding standards. But as another commenter mentioned, it declines with scale; this is why Facebook spent so much resources into trying to make webapps on mobile work, because their application size and compile times just got out of hand. It's possibly also a reason why they split off Messenger from the main app at some point.