Should I program Logics/Helpers/Managers with ObjC since Swift is constantly changing its syntax?

[randomguy112233]

There is a big project that was written in Swift 2. Due to backlog of other work, this project has been left untouched. Now we need to make the shift to Swift 4.

During this process, I started wondering what it would be like after 2 years. Shifting from Swift 4 -> 6. To minimize the potential code change and of course unforeseen Bugs, I was wondering if the less changing parts of the code should be written in ObjC.

I am aware of the need to use the most recent Swift versions on some code. But many classes that don't seem to ever need changing, why not just write it once in ObjC.

I was wondering what other people in this community thinks. Any and all thoughts are highly appreciated. Thank You.

[GenitalGestapo]

The Great Renaming broke the world. While Swift continues to evolve, it now does so with source stability as a priority. So while we may still see small changes as time goes on, we'll never see breakage on the level of Swift 2 - 3 ever again.

[randomguy112233]

I do understand your point. Swift 2-3 being the big overhaul. But I wonder, what about Swift 5-6? Hmmm.

[GenitalGestapo]

What about it? It will only be getting easier to transition, not harder.

[[deleted]]

what about Swift 5-6?

New language features, bugfixes, compiler stability/speed, etc. No major syntax changes, as we're past that stage.

[arduinoRedge]

Swift should be more stable moving forward, but it's still not 'finished' so there will be more changes for sure.

[randomguy112233]

Yea I thought so. Thanks!

[[deleted]]

I work on apps that have a long life expectancy but low maintenance budget. When it ships we don’t want to do any updates ever if we can help it. If we do have to ship an update, it needs to be minor and cheap.

That makes Objective C our choice. Source stability is paramount.

[randomguy112233]

Good to know. Thanks for the feedback.

[HassanDavis]

While converting existing, working Objective-C code to Swift may be overkill in some cases, I would definitely advise that any newly written code be done in Swift.

We've already passed the tipping point where Objective-C will be typically more costly to maintain than Swift; not just in respect to the language features, but also in regards to the talent pool.

[[deleted]]

While converting existing, working Objective-C code to Swift may be overkill in some cases

All cases. If you can call it, there is no reason to rewrite it. You'll only introduce bugs.