Swift learning path
Build a practical understanding of swift learning path from the underlying principles.
LANGUAGE · 7 ARTICLES
Swift & Objective-C
Go beyond memorizing syntax and understand why the language rules exist, from fundamentals and memory to concurrency and the Objective-C runtime.
Topic map
What this topic covers
Types and memory
Build a practical understanding of types and memory from the underlying principles.
Swift concurrency
Build a practical understanding of swift concurrency from the underlying principles.
Objective-C
Build a practical understanding of objective-c from the underlying principles.
Start here
New here? Start with these
A guided path from fundamentals to the next step.
All articles
All articles
Why Swift Was Created: Why Did Chris Lattner Abandon Objective-C?
Anyone starting iOS development has wondered at least once: "Why did Apple create Swift from scratch instead of sticking with the Objective-C it was already using?"
Read articleObjective-C Memory Management History: From MRC to ARC
If you work on iOS development, there’s probably something you’ve wondered about at least once.
Read articleObjective-C nil vs Java null: Why Do They Behave Differently?
There’s one thing that really confuses developers new to iOS.
Read articleObjective-C: A Complete History, the Language Jobs Loved (Including the Origin of the NS Prefix)
When you start studying iOS development, there’s one language you’re bound to encounter: unfamiliar syntax filled with brackets and mysterious prefixes like NSString.
Read articleWhy Does Objective-C Use Square-Bracket Syntax? (The Secret of Message Sending)
It’s easy to feel confused when you first encounter Objective-C code after starting to study iOS.
Read articleObjective-C at-sign (@) syntax: Why does everything start with @? (Complete Guide)
When you first open Objective-C code, one thing immediately catches your eye.
Read articleDefining Custom Swift Error Messages: A Complete Guide to LocalizedError (with Examples)
When building an app with Swift, you may have caught an error with do-catch, only to find that the message displayed on screen was less than helpful.
Read article