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

The Coming of Swift 3

Hi there. I know this has been discussed in a couple other posts, but I was just hoping for a detailed opinion. With the coming of Swift 3 (possibly very soon with the update of macOS Sierra Sept. 20), is this a bad time to take the Treehouse Swift 2.0 course? Swift 3.0 seems to be a big change in terms of syntax, and even 2.3 seems different than 2.0. I'd love your opinions. Thanks!

3 Answers

I find his opinion a bit discouraging to someone who is seeking to learn Swift. I disagree on the "debate" part. Swift is one of the fastest growing languages and the majority of iOS developers are switching to Swift. Objective-C may have been around for many years, but it's a very complex language to learn, and hence the birth of a new language.

Sam, if you want to learn Swift, my suggestion is to start with 2.0 and don't wait for new courses on 3.0. Yes, you may find changes later on, but they will be very easy to understand and adapt. I started with Swift 1.3 and I am very happy with what I have learned and the progress I made. And to be honest, I LOVE swift because it's a very very elegant language.

I hope that you don't get discourage and continue learning.

Good luck

Jason Anders
Jason Anders
Treehouse Moderator 145,863 Points

Hello Jhoan Arango

Sorry that you don't agree with my "personal" opinion. And, I don't agree with your "personal" opinion.

I would never discourage anyone from learning anything, and no where in my personal opinion did I say "do not learn Swift". That is entirely up to the individual, as are opinions.

As for the debates, there are hundreds of websites, blogs, and posts that I have read regarding the "debate" on whether Swift is a good thing or a bad thing. Just do a quick Google search and you'll see!

Also, I am very proficient in Swift 2 (I also started with the original Swift), but I don't find elegance anywhere in it. Java and Objective-C are very much more elegant and proficient in my opinion. Even Ruby is cleaner and more straightforward than Swift.

So, I apologize if you misinterpreted my "opinion" on this subject as being discouraging, as that is not the intent (or the purpose) of an opinion. Everyone is entitled to one, and just because mine differs from yours does not make either one more right or wrong. And, while I don't agree with yours, I still respect and honor your opinion.

When one researchs something, one will hear both sides. It's then up to the individual to make his or her own decision on what to do based on that research and all the opinions brought forth.

I would agree with Jhoan.

For work, I had to learn Swift when it was first introduced. I'm still using what I first learned about Swift every day, even though there has been major version updates since the beginning. The core language concepts, syntax, and conventions have persisted through its evolution so far. Personally, I haven't felt like I had to learn anything over again with Swift. I've also coded in Objective-C, but prefer Swift for its more intuitive, contemporary style and expressions. Looking forward to Swift 3.0!

Jason Anders
MOD
Jason Anders
Treehouse Moderator 145,863 Points

I may be in the minority of opinion here, but I have abandoned Swift, personally. In what took other languages many, many years to reach a version 3, Swift has done so in ~2 years. So, I've given up learning Swift, because as soon as I learn it, there are so many changes made, I feel like I'm learning it all over again.

There is still much debate as to whether or not Swift will actually survive (or go the way of cassette tapes). So, for now, I'm staying with Objective-C and Java.

In time, if Swift survives and becomes a bit more 'stable,' I may revisit it. But, for now... no thank-you!. :)

:dizzy: