3 ms·
If you have people who know Objective-C, there's no gain in being "forward thinking" for its own sake. But if you're not playing with your own money, sure, why
by pavlov 10y ago
If you have people who know Objective-C, there's no gain in being "forward thinking" for its own sake. But if you're not playing with your own money, sure, why not spend extra development time to bring everyone up to speed on what Swift looks like this year - it won't make the app any better and will cost more, but improves the team's résumés.
- ruleabidinguser 10y agoI think better support and better code is a benefit, but thats just me. You sound like youve gotten rubbed in the past by this, no? And by the way, "forward thinking" is not something you can be or do for its own sake. Think about it. That doesnt even make sense.
- LeoNatan25 10y agoDon't forget the next year, when Apple yet again breaks the language and you have to take all your large codebase and convert it to Swift (x+1).
- melling 10y agoThere might be a handful of changes in the future but it won't be anything like 2 to 3. I imagine that the automatic converter will get most of them. Swift is open source so you'll know all changes well in advance.