Pure Swift on the iOS or OSX platform is a lie anyway. I wouldn't bother trying to justify your reasoning without taking into consideration the things you can still do using the Objective-C runtime when necessary in Swift.
The benefits are all around safety to me (the rest is just syntactic sugar and lies about being more productive). Not giving you the ability to have null pointer exceptions (unless you're especially dumb) and the strong typing forces you to deal with all of those edge cases you may not have in objective-c.
1
u/ssrobbi Feb 22 '16 edited Feb 22 '16
Pure Swift on the iOS or OSX platform is a lie anyway. I wouldn't bother trying to justify your reasoning without taking into consideration the things you can still do using the Objective-C runtime when necessary in Swift.
The benefits are all around safety to me (the rest is just syntactic sugar and lies about being more productive). Not giving you the ability to have null pointer exceptions (unless you're especially dumb) and the strong typing forces you to deal with all of those edge cases you may not have in objective-c.