Feet in Both Worlds: From Objective-C to Swift
summary
Claims that Swift’s Objective‑C bridge imposes real semantic and engineering weight: a ~200‑page interop surface, keywords like dynamic and @NSManaged, and surprising hacks such as a Box wrapper and manual adapter shims for enums structs and generics. Reports from Khan Academy: a codebase becomes ~30,000 lines of Swift, migration slows the team for months but yields a working, swifty UI stack by layering Objective‑C bridges, shims, and closure‑based adapters.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:54History of ObjectiveC
- 3:43Swift and ObjectiveC
- 4:43Integrating Swift
- 5:50Weight of ObjectiveC Swift
- 6:41Implicit or Explicit
- 7:33Exceptions
- 9:02Managed
- 11:11Copy
- 12:40keyword arguments
- 13:57Dynamic
- 15:24Cycle Detection
- 16:48Opportunity Cost
- 19:05Libraries
- 20:23Storytime
- 22:26Problems with Swift
- 23:21enums
- 26:23box
- 28:54cardsuit
- 30:35user
- 32:21extension
- 33:15generics
- 33:45Swift example
- 36:45Untyped section
- 38:41Conclusion
related talks
45mMoving from Objective-C to Swift — Is It Really That Simple?
39mSwitching your brain to Swift
04mSupporting Objective-C in a Swift codebase
47mTime Traveling With Swift: Where We Started, Where We Are, and Where We’re Going
57mCatching up with Swift
50mTime traveling with Swift
58mSwift: safety, ergonomics, productivity and legacy preservation
19mUsing C, C++ and Objective C frameworks in Swift apps