Objective-C vs Swift
Discussions focus on the shift from Objective-C to Swift in Apple iOS/macOS development, debating Objective-C's declining relevance, continued use in legacy apps, and preferences between the languages.
Activity Over Time
Top Contributors
Keywords
Sample Comments
ObjC ain't going anywhere.
Aren't you worried about Apple killing ObjC down the line?
ObjC is mostly dead, and most Swift devs are not comfortable with C++.
I'm not mac dev but wasn't apple all in on objc back then and these days it's more swift? that is pretty big shift, I'd assume for the better for most parts.
A lot of major iOS apps still use ObjC
Objective C is good once its philosophy "clicks" with you, but any new development I would start in on Swift. Swift is a much nicer language, feels like compiled Python.Same with Android, I would choose Kotlin before Java if it was my choice.People still working with Objective C might be like I recently was: maintaining a sizable codebase which, unless Apple breaks something, porting to Swift is not justifiable to management.
Objective-C would be a bad idea now, it seems to be replaced by Swift at an impressive rate.
Giving devs a way out of ObjC is a pretty big draw :).
Objective-C is a dead end. Swift.
Apple supports Objective-C, which is arguably just as bad as C++.