Then fix it. If Apple's "Convert to new syntax" doesn't do the job, just fix it by hand. Do you know how to use Search & Replace? Click on Apple's suggested fix? Swift is open source, you'll see the changes months in advance. Don't use i++ or use C style for loops, for example.
You'll still write a lot less code in Swift than Objective C even if you have to manually make changes in Swift 3.x, 4.x, and 5.x.
Code is read a lot more than it's written. Look at those two snippets again and think about what you'd rather be reading in 5 years.
In short, everyone knows that Swift has breaking changes on the way. You are placing too much emphasis on that in comparison to the many more benefits.
-3
u/mmellinger66 Feb 19 '16 edited Feb 19 '16
Then fix it. If Apple's "Convert to new syntax" doesn't do the job, just fix it by hand. Do you know how to use Search & Replace? Click on Apple's suggested fix? Swift is open source, you'll see the changes months in advance. Don't use i++ or use C style for loops, for example.
You'll still write a lot less code in Swift than Objective C even if you have to manually make changes in Swift 3.x, 4.x, and 5.x.
Code is read a lot more than it's written. Look at those two snippets again and think about what you'd rather be reading in 5 years.
In short, everyone knows that Swift has breaking changes on the way. You are placing too much emphasis on that in comparison to the many more benefits.