>> *Regretfully considers years spent using Objective-C*
Don't regret it. I can potentially see Apple backtracking on Swift realizing that maintaining bindings to native libraries is too costly, they will potentially revert back to Objective-C. Your experience here will make you a decent manager (unless you enjoy coding)
The critical part in Objective-C is not the "Objective". It is the fact it can consume native C libraries.
This view may get a bit of dislike from avid Swift fans which is fair. However I strongly recommend them to not completely disregard Objective-C. Unless Apple adds a very small C-compiler to their Swift toolchain so that it can consume native C binaries, the future could very much revert back to Obj-C. Same goes for Rust and Go-lang to some extent. Even though Go is "kinda" close with its C preamble stuff.
Time will tell. Thus far time has strongly hinted at C compatibility being the winning formula. For example pick any two languages and try to get them to communicate directly without C somewhere in the mix!
Biting the hand that feeds IT
