Swift vs. Objective-C

Not really an epic battle.

Transcript

1. SWIFT VS. OBJECTIVE-C THE EPIC BATTLE
2. OBJECTIVE-C: STILL REALLY FUN.
3. - (void)updateWithDictionary:(NSDictionary *)dictionary context:(NSManagedObjectContext *)context { [self.remoteToLocalAttributeMap each:^(NSString *remoteName, NSString *localName) { id remoteValue = dictionary[remoteName]; if ([(NSNull *)remoteValue isEqual:[NSNull null]]) return; if (self.remoteDateFormats[remoteName]) { remoteValue = [NSDate dateFromString:remoteValue format:self.remoteDateFormats[remoteName]]; } [self setValue:remoteValue forKeyPath:localName]; }]; } (Yes, this is fun)
4. ▸ Super dynamic ▸ Meta-programmable ▸ More mature ▸ Strong ecosystem support
5. SWIFT IS PRETTY AWESOME.
6. private func createOrUpdateLocations(dicts: [NSDictionary]) -> [SaucerLocation] { let realm = RLMRealm.defaultRealm() var locations = [SaucerLocation]() realm.transactionWithBlock() { for dict in dicts { var instance = SaucerLocation.findOrCreate(dictionary: dict, inRealm: realm) locations.append(instance) } } return locations }
7. ▸ Type safety ▸ Generics ▸ Succinctness ▸ Beautiful "block" syntax
8. OBJECTIVE-C: LIKELY NOT "THE FUTURE."
9. ▸ Not going anywhere ▸ Not getting any better ▸ Solid, but stuck in the past
10. SWIFT: STILL WITH SOME WARTS.
11. ▸ Compiler has a couple of bugs ▸ Works with 90% of UIKit/Foundation well ▸ CocoaPods support forthcoming ▸ Banner features still need some TLC
12. WHY CHOOSE?
13. SPOILER ALERT: YOU MIGHT NOT NEED TO
14. ▸ Interoperability still an option, albeit tricky ▸ "Pure Swift" projects are easiest to manage
15. BUT IF I HAD TO?
16. Learn Objective-C first, then Swift. Build a few Objective-C apps first, then some Swift ones.
17. REALLY? NOT NECESSARILY.
18. If you're comfortable digging into Swift first, do it.
19. Objective-C is worth learning, even if it's not the future.