4 ms·
ObjC ain't going anywhere.
by fleitz 10y ago
ObjC ain't going anywhere.
- pjmlp 10y agoThe amount of ObjC sessions at last WWDC 2015 and the upcoming WWDC 2016 send another message.
- Karunamon 10y agoYup. The Standard Apple Deprecation Cycle works something like this: 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.
- fleitz 10y agoObjC is dead when swift no longer spends most of its time calling in to ObjC for the typical iOS/OSX app.
- pjmlp 10y agoIn case you didn't got the memo, GDC and XTest are being re-written in Swift, it will eventually happen to other frameworks when it makes business sense to do so. Let's see what else gets announced at WWDC 2016 and how many talks do show Objective-C code.
- fleitz 10y agoGDC is C code... I'm talking UIKit. Totally agree that on the WWDC they announce that UIKit is written in swift then it's officially dead.
- Eric_WVGG 10y agoObjC will be around much longer than 3 years. It can't be deprecated until most of OS X is rewritten. Remember how long it took them to get rid of the Carbon Finder?
- pjmlp 10y agoSure, but the way it is being handled is a sure signal were things are going. 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.