Moreover, the app now featured a new onboarding process: While the old one took more than a month and multiple engineers to implement, the new onboarding with Swift was completed within a week with only one engineer. And with Swift, that was a project that took a week for one engineer. On the old, that was a project that took more than a month, with multiple engineers.
By the time the company was done recreating it in Swift, they had something that performed the same tasks in less than a third of that.īy the time we were working on this Swift project, we were also working in parallel on revamping the entire onboarding flow of the app. Over the years, the original version of Lyft had ballooned to 75,000 lines of code. This also means reduced duration needed to complete the job. This means lesser manpower is needed to develop the same amount of functionality or app. Swift needs lesser code to Lesser code develop the same functionality, as compared to Objective-C. Craig Federighi, Apple VP of Software Engineering How it affects you as an application owner – The Benefits Rapid Development People here are idealistic yet really pragmatic, and I think you see that as an Apple characteristic in many, many elements of what we do. And this Apple will still continue support to Objective-C and is not planning to pull the plug anytime in the near future. They can start upgrading and enhancing to the newer platform, taking advantage of the existing Objective-C sections, and can then move slowly towards Swift in due course.Īpple also understands the importance of Objective-C and believes that a shift to Swift cannot be done overnight.
This primarily is advantageous for the big Objective-C applications which cannot be re-coded into Swift but would like to make a switch gradually. So, they both are compatible and can be used side by side, as of now at least. Or start using Objective-C routines in new Swift Projects. Slowly put in new Swift code into the existing Objective-C Project. That said, there are multiple approaches to how they can co-exist and how the developers can take advantage of this coexistence. They are not mutually exclusive but the intuitive design of Swift allows Objective-C to co-exist along with it.
The swift design allows it to be interoperable with Objective-C. But in the here and the now, the two must learn to coexist peacefully. Objective-C is showing its age and will, eventually, be much less prevalent. It’s no question - swift is the new toy and marked as the future. Swift on the other hand came into existence to replace an aging programming language with a modern technology platform. Objective-C was created and tuned for IOS development from birth.
0 kommentar(er)
