[tedkalaw]

sometime in the future, Apple will begin releasing swift-only APIs. it's unclear that one should "drop everything", but swift usage will only increase in the future. in addition, as a company, it will become difficult to hire new people if you don't try to move to swift at some point.

ymmv, of course. i'm new to iOS land and i write objective-c exclusively during my day job. that being said, the difficulty in iOS development (in my experience) is not in the language, but the APIs, abstractions, and patterns - and they are the same regardless of whether you're using swift or objective-c

[HaloZero]

I mean sometime in the future will probably be pretty far away for Obj-C developers.

“Objective-C is not going away. We still love Objective-C as a language; we still very much depend on Objective-C and do a tremendous amount of work in Objective-C here internally at Apple,” Federighi told Ars. “We’ll be supporting Objective-C and continuing to evolve it as necessary to fit into this evolving world. We do think that Swift is the language that we recommend for new developers to our platform who are investing for the future and building new apps. We think Swift is absolutely the right place to start. But we’ll continue to maintain, advance, and support Objective-C for as far as we can see.”

From http://arstechnica.com/apple/2015/12/craig-federighi-talks-o...

[padobson]

The beauty of making Swift open source means that changes to the language will be influenced by the broader community. If Apple finds this kind of thing useful, then perhaps the APIs will get the same treatment and we'll start to see an improvement in the iOS dev experience.