@gerryc 100% Swift. There is zero reason not to.

@jonduenas @gerryc totally agree. Though getting a bit familiar at some point with Obj-C could be useful, especially since there are some still valid libraries out there. Swift can bridge the headers automagically, but if you need to debug, being able to read Obj-C will be important. But to start, Swift is the way to go.

@titociuro @gerryc Sure, but it’s one of those things that as the years go by will be less and less valuable a skill. If you get proficient with Swift and then get hired by a company that still uses Obj-C, you can pretty easily pick it up then. But those companies are becoming more and more rare. There’s just way more valuable things to spend your time learning.

@jonduenas @gerryc agree, agree.

@titociuro @jonduenas I'm grateful for your helpful feedback! On a related note, would either of you be able to point me in the right direction regarding #coding bootcamps? Context:
https://mstdn.party/@gerryc/109690877727220657

@gerryc @jonduenas sure thing! Have you heard of 100 Days of Swift? I’m a fan of Paul and love the contents he puts out. https://www.hackingwithswift.com/100. @StewartLynch is awesome as well. YouTube: Sean Allen, Swiftful Thinking, Kavsoft, iOS Academy, Let’s Build That App and many others. Last but not least, I have found really good content at Udemy. Not free, but about $9 bucks for the course. That’s like… two lattes 😉

@titociuro @gerryc @StewartLynch These are good. I think the real question is whether you should start with UIKit or SwiftUI. Solid arguments for either really. You should probably learn both at some point. SwiftUI is definitely easier to get started. But a lot of great early learning content out there is UIKit. Angela Yu’s course on Udemy being one that got me started. Might also depend if you know other languages or starting from nothing.