Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

CoolIndian

macrumors newbie
Original poster
Aug 8, 2015
17
1
India
i am new as a iPhone developer and start learning Swift so should i continue learning Swift, or beginning from Objective-C first .
 
Can you give us some insight into your goals? Are you training for a job or do you want to make games or personal apps? Do you want to be an Indie consultant (programmer for hire)?

Is this a long term career move?

In some cases, you'd have to guess the long term popularity of Swift vs ObjC. In other cases, the tools used don't matter to the consumer.
 
Can you give us some insight into your goals? Are you training for a job or do you want to make games or personal apps? Do you want to be an Indie consultant (programmer for hire)?

Is this a long term career move?

In some cases, you'd have to guess the long term popularity of Swift vs ObjC. In other cases, the tools used don't matter to the consumer.
i m training for a carrier as well as personal apps, i think swift is easy .
 
i m training for a carrier as well as personal apps, i think swift is easy .
Training for a carrier? you mean career?

In that case, Swift might be the best choice. Keep an eye on the job market to see how many jobs are asking for Swift and how many years they want to qualify for the work.

Don't forget that Swift and ObjC are just languages. Languages are one small part of the total package. Knowing programming logic, APIs and other things are a very important part of the whole package.

Look at what the jobs are asking for, networks, RESTful, CoreData, SQL, etc... lots of things to keep track of.

Many of us are fluent on several languages, it's easier once you've mastered the 1st one.
 
Training for a carrier? you mean career?

In that case, Swift might be the best choice. Keep an eye on the job market to see how many jobs are asking for Swift and how many years they want to qualify for the work.

Don't forget that Swift and ObjC are just languages. Languages are one small part of the total package. Knowing programming logic, APIs and other things are a very important part of the whole package.

Look at what the jobs are asking for, networks, RESTful, CoreData, SQL, etc... lots of things to keep track of.

Many of us are fluent on several languages, it's easier once you've mastered the 1st one.
yes for career, i'm not new in this field now i m working on IBM Mainframes and i m good in others languages too.
 
yes for career, i'm not new in this field now i m working on IBM Mainframes and i m good in others languages too.
In that case, it might not matter which one you pick. In fact, you might end up knowing both.

ObjC has a HUGE following and code base, however, Swift would put you closer to the start of the language and seems to be gaining some ground.

It's undetermined what footing a "new to a game already well underway" language will have. _IF_ Swift was introduced several years ago, it would have a strong hold, but there are SO many advanced apps already that it's hard to tell if a company will invest in rewriting a current app. There doesn't seem to be enough of a benefit (if any) to dumping current ObjC code just to be able to say "written in Swift"

New development might be a different story, but remember, many brand new apps might be playing catch up at this point.
 
  • Like
Reactions: page404
In that case, it might not matter which one you pick. In fact, you might end up knowing both.

ObjC has a HUGE following and code base, however, Swift would put you closer to the start of the language and seems to be gaining some ground.

It's undetermined what footing a "new to a game already well underway" language will have. _IF_ Swift was introduced several years ago, it would have a strong hold, but there are SO many advanced apps already that it's hard to tell if a company will invest in rewriting a current app. There doesn't seem to be enough of a benefit (if any) to dumping current ObjC code just to be able to say "written in Swift"

New development might be a different story, but remember, many brand new apps might be playing catch up at this point.
Thanks a lot..
 
Learn Objective-C and write in Swift.

They're inneroperable and many resources are (and are still being) written in Obj-C. Plus, many of Apple's frameworks are in obj-c, so it'll help you to understand the some of the oddities that comes with working with Swift and the entire runtime.

Write with Swift because it is a much better, safer, and modern language that's easy to understand on the go. Plus, you won't have to convert a larger code base down the road if that becomes necessary.
 
If you have no existing code to deal with, go ahead and learn swift, it is a simpler and shorter learning curve. However if you plan on having a professional career doing this you will sooner or later be interacting with objective C code so its good to know, but definitely a much larger learning curve.
 
Began an app with Objective-C but after apple didn't accept my app I started again in Swift.
And its: WONDERFUL! (but… "compiling swift-source files" is super-slow) :D
 
Just learn both of them, and pick which one you prefer (probably swift).

Objective-C is not a difficult language to learn (it's mostly C which it sounds like you already know and the rest is mostly identical to Swift), and a good Objective-C foundation will really help as a Swift programmer since most of the APIs you're calling were written in Objective-C.

Swift is the future in my opinion, and long term that's what you will need to know. But Objective-C is still a big force now and it's not going away quickly.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.