Swift on the other hand hasn't been out long enough for there to be enough answers on the knowledge base websites to cover all issues that will arise in the learning curve.
Between Apple's excellent free books and StackOverflow (which is brimming with Swift questions and answers) that is not at all true. Any issue you run into coding Swift is well covered by online resources already.
Remember how long it took to lay Carbon to rest.
Carbon was an entirely different set of frameworks.
Swift on the other hand uses all of the existing frameworks - only the have tweaked the Swift definition of the endpoints such that it's more Swift friendly (like knowing when arguments or return values will or will not be null for sure).
So there is zero Carbon-Like transition time involved.
I'm not drinking the Apple Kool-Aid, I am telling you what is happening in real-world iOS development today. If you learn anything but Swift you are going to be WAY behind state of the art inside a year.
I'd say it's 50/50 whether or not Swift will get enough traction to continue on.
Jumping horny ghost toad of Fernando, you are not really that stupid, are you? Please tell me you are just trolling? You really don't understand what happens when Apple puts weight behind a development technology? Wow.
In one year I will re-link to your post in EVERY Slashdot post you make.
At this point I wouldn't even buy whatever CEREAL you normally buy, with judgement like that.
Guns. Specifically, WWII era U.S. infantry weapons. Good for making old hard drives unreadable; good for defending the household. I can probably find other uses should the need arise.
Cheers,
Dave
There's a very strong case to be made for Swift first going forward, and not many seem to be making it or understand the iOS dev world at all.
I speak as someone who has been developing iOS applications since somewhat before the release of the iOS SDK way back when.
I don't think anyone outside those paying the closest attention to iOS development realize how rapidly Swift is being adopted, especially by those who have been doing Objective-C the longest.
That's the core aspect of this I don't think people understand. iOS developers by and large are a very pragmatic bunch. Even those who love Objective-C (and there are many) are perfectly happy to move to something new that makes development even faster so they can accomplish the end goal of building apps for people.
That's really what iOS developers really care about, delivering apps. Anything that helps they are on-board with, and you can plainly see Apple is backing Swift big-time so the developers are hitching to that very powerful wagon.
If I were advising ANY developer new to iOS, I would absolutely say go Swift first. Someone said there's more Objective-C educational material? Technically true, but also consider how much of that is outdated. With Swift anything you find (and there is a LOT right now) is guaranteed fresh.
If you worry the iOS development market is overcrowded, don't - experienced developers for all backgrounds are badly needed all over.
Swift isn't finished. From what I've read, they expect to make syntax-incompatible changes.
That was before Swift 1.0 introduced with the final XCode 6 and iOS8. They aren't breaking syntax anymore...
And even when they were, it was usually pretty minor things to fix.
I'd imagine it will eventually (over a couple of decades)
HA HA HA HA HA HA HA
You don't know Apple, or iOS developers. Dominant over ObjC within two years (and by the end of next year that prediction will probably seem ridiculously conservative).
Good day to avoid cops. Crawl to work.