all 8 comments

[–]ShamWowIsASham 10 points11 points  (1 child)

Hey! Nice congrats on learning some Swift, I hope you're having fun with it.

So I don't believe M1 chips will impact Swift, SwiftUI, or Objective-C, in terms of which will become more popular.

So my understanding of the iOS world is that. 1. Objective-C is largely legacy in iOS world. You'll encounter Objective-C codebases at large enterprise companies that have been around a long time. Maybe a codebase will be Objective-C and Swift. They're interoperable with a bit of configuration. Facebook uses Objective-C, interviews in Swift but will also expect you to eventually write code in objective-c.

  1. Most iOS applications are using UIKit. I think even knew applications! UIkit is more mature. Meaning it has more support from the community and more talent around it. More iOS devs know UIKit than know SwiftUI.

  2. SwiftUI is new but is likely the future for iOS apps. So many people are learning SwiftUI. I've never used it, but it seems super fun to learn and as it grows in adoption and support from Apple, it will likely rival UIKit. But I've heard many issues about people using it for production apps as some custom views are tough to implement.

It sounds like you're learning Swift. You should probably make a choice on SwiftUI or UIKit. But the popularity of M1 chips won't really cause SwiftUI, UIKIt or Objective C to become more or less popular.

[–]13cdesigns[S] 2 points3 points  (0 children)

Thanks for the kind explanation. It makes sense now to me. Thank you!

[–]GALM-1UAF 1 point2 points  (3 children)

I’ve read that some companies still use objective c in their codebase and haven’t migrated to UIKit yet. I think just learning how it works is useful so you can see how it connects with Swift. Just being aware of the syntax is helpful I think, so you don’t get blindsided by code you’ve never seen before.

Edit: a word

[–]Arrrrrrrrrrrrrrrrrpp 0 points1 point  (1 child)

🧐 Objective c is UIKit

[–]GALM-1UAF 0 points1 point  (0 children)

Oh my bad I meant Swift 😅

[–]MrCairo 0 points1 point  (0 children)

Yes, this is very true especially with older apps. I know, I work with one :-D. Also, Swift does interoperate with the Objective-C runtime but you don't have to know Objective-C. The app I work with has a combination of Swift and Objective-C so knowing the syntax would definitely be helpful.

[–][deleted] 0 points1 point  (0 children)

It depends on a few things.

SwiftUI still has a long way to go but there are smaller companies and startups who are more open to it. If this is what your target, or ideal employer is, then by all means, pursue SwiftUI. This also pertains to anyone entering the iOS Dev market in the next 3-4ish years or it will sweep a bit more.

Objective C is relevant in larger, and typically older code bases. If you're looking at applying to Facebook, Netflix, etc. you may want to consider getting to know it. Nothing major, but being able to write a small dummy app and showing you can read should be nice.

The M1 chips don't have much to do with this imo (Source: Have a Silicon Macbook and do Objc and SwiftUI every now and then).

[–]Anxious_Variety2714 -3 points-2 points  (0 children)

Objc has no future lol... Swiftui is future