Moving from Objective-C to Swift - Swift Mumbai #3

Swift was released almost 4 years ago now and clearly, it is the way forward in developing apps for the iOS platform. The question a lot of people are asking now is should they move their codebase from Obj-C to Swift? The answer to that question depends on a variety of factors. There are many people who will be championing Swift as the answer to everything. It certainly could be in the future, but in the present, it is not. It is the answer to a major portion of problems that plagued or currently plague iOS/Mac development, but not all of them. I will be proposing a multitude of scenarios in which a move from ObjC to Swift would be detrimental to the long-term prospects of a project and also scenarios where moving to Swift would be enormously beneficial.

About the Speaker: Atharva Vaidya is an iOS/Mac Developer for 6+ years now. Currently working at Medal.tv remotely from Mumbai.
You can find Atharva at -
https://twitter.com/atharva_vaidya
https://github.com/AtharvaVaidya
https://www.linkedin.com/in/atharvavaidya

Presented at Swift Mumbai - Chapter #3 Meetup: https://www.meetup.com/Swift-Mumbai/events/249701161/

Watch the Presentation at: https://youtu.be/bcAZfowt_lE

Transcript

1. About Me
2. Is it time for Swift?
3. State of Swift
4. ABI Stability
5. Why move to Swift?
6. We can write clearer, safer, faster code.
7. Productivity
8. https://page.mi.fu-berlin.de/prechelt/Biblio/jccpprt_computer2000.pdf
11. Why not move to Swift?
12. If it works, don’t fix it.
13. App Size *Until Swift 5.0
14. Low level APIs
15. Migration Costs
16. So what's my hot take?
17. Writing a brand new app? No interaction with low-level APIs? Migration costs not an issue? Go for it.
18. App size matters? Busy shipping new features? Extensively use low-level APIs? Wait for Swift 5.0
19. Thanks! @atharva_vaidya