There is always a penalty for using bleeding edge stuff. In the case of Swift, there has been significant penalties for early adopters as people have already discovered.From my understanding, people who have deployed Swift 1.x apps before will be forced to update to Swift 2 if they want to target anything specific to iOS 9 or OS X 10.11 (assuming those SDKs will not be available for Swift 1.x on Xcode 6 at least officially). Otherwise, it is safer to stay with Swift 1.x on Xcode 6 for now (and even more safer if you had not adopted Swift at all so you can target latest APIs in Xcode 7 without penalties).They have not officially confirmed yet which older iOS or OS X versions will be (and not be) supported for Swift 2. So, I am not sure how one can make a safe and informed decision on a migration path for a significant project using Swift.What is your compelling use case that requires you to convert an existing project to Swift 2? Worth thinking about.If the new language constructs, l
Topic:
Programming Languages
SubTopic:
Swift
Tags: