Developers are in no hurry to implement

This shows that Swift is becoming a more mature and stable language. Now, if developers want to roll back a certain functionality, they give. A year or even two for a transition period — this is enough time to switch to a new version. Usually, new features in projects, because most updates can be use only on the latest versions of iOS. For example, the native StoreKit framework. The community was very much looking forward to its update in order to migrate from the first version, which at that time was very outdate and containe many “bearde” bugs.

There are much more interesting alternatives

The announcement of the second version took place together with the announcement of iOS 15. At that time, the current version for users was iOS 14. Since the general rule is to support at least -1 current version, at that time most products supporte iOS 13 and iOS 14. However, for a full migration to the new version of StoreKit had to drop all versions Singapore Phone Number List except 15 or support both implementations at the same time. MYTH 4 Swift is fully adaptable for non-iOS projects Objective-C is a language locke on the macOS operating system. Previously, no one even trie to use it for another development. In contrast, Swift is an open-source project that can be use for tasks outside.

The main obstacle is need to invest

Scripts for local tasks are written in Swift. Also, IBM trie to invest in the Swift backend. In the end, nothing significant came of it. In addition to AERO Leads local small projects, Swift remaine a technology that does not go beyond the boundaries of the Apple ecosystem. in a community that will not grow by itself. In addition, from a performance point of view, for the same backend.