Not everyone wants C to stay around.
1. New shiny thing is announced
2. Old busted thing starts getting talked about less
3. New shiny thing becomes the default, old busted thing hidden away
4. Official deprecation warnings issued
5. Old busted thing stops being supported. Apple being Apple, this quickly leads to
6. Old busted thing stops working altogether after something like an OS update.
We're currently at step 2. Originally I thought that Obj-C would be kicking around for a lot longer, but given that Apple dropped an entire CPU architecture in relatively short order, and their scorched earth attitude towards backwards compatibility...
I give it 2, maybe 3 years before ObjC isn't officially supported in Xcode anymore.
Let's see what else gets announced at WWDC 2016 and how many talks do show Objective-C code.
Totally agree that on the WWDC they announce that UIKit is written in swift then it's officially dead.
Remember how long it took them to get rid of the Carbon Finder?
Apple even mentions Swift as a C and Objective-C replacement on their documentation.
Of course, it doesn't make business sense to stop the engines and rewrite all the stuff.
You mean like the "Framework of the day" on web land?
Or the "rewrite your app with each Android version" that you cannot get?
Or "your language just got replaced" on iOS land?