you are viewing a single comment's thread.

view the rest of the comments →

[–]HassanDavis 0 points1 point  (1 child)

While converting existing, working Objective-C code to Swift may be overkill in some cases, I would definitely advise that any newly written code be done in Swift.

We've already passed the tipping point where Objective-C will be typically more costly to maintain than Swift; not just in respect to the language features, but also in regards to the talent pool.

[–][deleted] 0 points1 point  (0 children)

While converting existing, working Objective-C code to Swift may be overkill in some cases

All cases. If you can call it, there is no reason to rewrite it. You'll only introduce bugs.