Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

iOS

Posted by Brendan Whiting
.a{fill-rule:evenodd;}techdegree seal-36
Brendan Whiting
Front End Web Development Techdegree Graduate 84,738 Points

Swift, Swift 2.0 (or Objective C)?

I was partway through the Swift course, but now there's also Swift 2.0. Should I just switch over to 2.0? It seems like I would end up repeating a lot of things but I would prefer to learn the newer version I think. Also is it worth doing the Objective C course?

1 Answer

ianhan3
ianhan3
4,263 Points

It's definitely worth knowing the new syntax changes in Swift 2.0, however, you can pick most of those up just by reading the documentation and doing your own projects. It becomes frustrating when some of the older swift tutorials aren't updated and your app crashes but, on the other hand, it makes you become more self sufficient to figure out what's wrong.

You'll be repeating a lot of the same content for the Swift 1 and 2 courses simply because a lot of the concepts don't change. Strings are strings, protocols are protocols. Things like println() became print() but you'll just naturally pick those little changes up as you use them away from Treehouse.

Objective-C is totally up to you. Do you want to become an iOS/ mobile dev? If yes, then it's pretty non-negotiable to have a pretty good understanding of C and Objective-C. You may have to refactor legacy code or (at the very least) read some Objective-C to understand what previous developers did. It also just has an outstanding amount more documentation since it's like a 20 year old language.

If you just want to build iOS apps for the future, you'll be alright with Swift.