I'm impressed that you are aware of the coding details of the "vast majority of projects" to be able to make such a determination that it "shouldn't take long".
As for supporting iPhone X, yeah, if you use Auto Layout correctly like they’ve been strongly suggesting and educating developers on
for several years now, it’s pretty painless to make the jump.
As for Swift version migration, I’ll admit it was an assumption. If people weren’t happy with Swift, I figure its growth in usage wouldn’t be explosive and many folks would’ve jumped back to Objective-C and/or cross-platform garbage by now. While it’s tough to say with much certainty, it is likely that that has
not happened.
Listen, if you don’t want to deal with a rapidly changing programming language, don’t use a young programming language. This much is basically
common sense. Even though it’s been a few years now, Swift still certainly counts as young (though I’ll go out on a limb in saying that I think Swift 3 will prove to be the worst the growing pains get from here on out).
Don’t like how often Swift changes? Use Objective-C if you’re more familiar with it. It’s very unlikely that end-users will notice any difference. Or better yet, get involved in the open-source project and make your voice heard as to why you think a change should or shouldn’t be made. Either way, it’s not my problem and I’ve already devoted more time to this post than it took me to migrate an app to support Swift 4, iOS 11, and iPhone X.
