+- Proxy Community (https://proxycommunity.com/forum)
+-- Forum: Technical Community Support (https://proxycommunity.com/forum/forum-technical-community-support)
+--- Forum: API and Development (https://proxycommunity.com/forum/forum-api-and-development)
+--- Thread: Objective C vs Swift: Which One Should You Learn for iOS Development Today? or Objective C vs Swift: (/thread-objective-c-vs-swift-which-one-should-you-learn-for-ios-development-today-or-objective-c-vs-swift)
Pages:
1
2
Objective C vs Swift: Which One Should You Learn for iOS Development Today? or Objective C vs Swift: - CipherNomadX - 28-04-2024
"Objective C vs Swift: Which One Should You Learn for iOS Dev Today?"
hey folks! 👋
sooo, i’m kinda new to iOS dev and keep seeing debates about *objective C vs Swift*.
swift seems cleaner and more modern, but i’ve heard some older apps still rely on objective C.
is it worth learning both? or should i just go all-in on swift?
also, do companies even care about objective C anymore? or is it all swift now?
kinda torn here—anyone got thoughts?
(ps: if you’ve switched from one to the other, how was the transition?)
thanks! 🚀
“” - CloudDrifter99 - 01-11-2024
If you're just starting out, Swift is 100% the way to go. It's way more beginner-friendly and has a ton of resources like Swift Playgrounds or Hacking with Swift (great site btw).
Objective C is kinda like Latin—useful if you're maintaining legacy code, but not something you *need* unless you're working on older apps.
Most new projects are Swift-only, so unless you're targeting a specific job with legacy stuff, I’d skip objective C for now.
Transitioning from objective C to Swift? A bit of a learning curve, but Swift’s syntax is so much nicer once you get used to it.
“” - maskedVoy_99 - 05-11-2024
Honestly, it depends on your goals. If you wanna work at a big corp or on older apps, objective C might pop up. But Swift is the future—Apple’s all-in on it.
I’d say learn Swift first, then peek at objective C later if needed. Tools like Xcode make it easier to mix both, but you’ll rarely *need* objective C these days.
Check out Ray Wenderlich’s tutorials—they cover both languages if you’re curious!
“” - deepDartX99 - 05-02-2025
Swift, no question. Objective C is clunky af compared to Swift’s clean syntax.
That said, if you’re into freelancing or niche jobs, *some* clients still have objective C codebases. But 90% of the time? Swift.
Transition was smooth for me—Swift just makes more sense. Apple’s docs are your best friend here.
“” - webEscapeX - 15-02-2025
I’ve worked with both, and here’s the tea: Swift is easier to learn, but objective C teaches you *a lot* about how iOS works under the hood.
If you’re serious about iOS dev, knowing a bit of objective C won’t hurt. But Swift is the priority.
For resources, Udemy has solid courses on both. Also, GitHub repos with mixed codebases can help you compare.
“” - shadowMimicX - 14-03-2025
Swift all the way! Objective C feels like writing an essay with a quill pen—doable, but why?
Most companies are migrating to Swift, and tools like SwiftUI are game-changers.
That said, if you *do* need to dabble in objective C, Stack Overflow is your lifeline.
“” - maskedExplorerX - 22-03-2025
Hot take: Learn Swift first, but don’t *ignore* objective C. Some older libraries/docs are still in objective C, and it helps to at least *read* it.
Swift’s interoperability means you can mix them, but tbh, I’d focus 80% on Swift, 20% on objective C basics.
For practice, try rewriting small objective C snippets in Swift—helps a ton!
“” - CipherNomadX - 27-03-2025
Wow, thanks for all the insights, everyone! 🙌
Seems like Swift is the move, but I’ll keep objective C in my back pocket for legacy stuff. Gonna start with Hacking with Swift and maybe dabble in some GitHub repos to see both in action.
Quick follow-up: Anyone know if SwiftUI changes the game even more? Like, should I jump straight into that instead of UIKit?
Thanks again—y’all are legends! 🚀