Apple is currently working on Swift 5.0, the next major version of its the coding language the company first introduced in 2014. As Apple prepares to release Swift 5.0, Ted Kremenek, who is leading the project, recently sat down for an interview with John Sundell on his Swift by Sundell podcast.
The new episode, titled "Pragmatic Priorities," is available to listen to starting today on iTunes and through the Podcasts app on iOS devices.
Kremenek is Apple's senior manager of languages and runtimes, and he is overseeing the release of Swift 5 and is Apple's voice on the project.
In the podcast, Kremenek covers topics that include how Apple plans new features for Swift, the process by which pitched ideas turn into release features, and of course, Swift 5.
Swift 5's major focus is long-awaited ABI stability (Application Binary Interfaces), and Kremenek goes into detail on how ABI stability was ultimately implemented and what changes needed to be made for Swift to become ABI stable.
With Swift 5, apps created with one version of the Swift compiler will be able to interface with a library built with another version, something that is not the case now.
The Swift by Sundell podcast with Ted Kremenek will be of interest to developers and those who use the Swift language and want to learn more about the changes and features coming in Swift 5.
Top Rated Comments
[doublepost=1551212910][/doublepost]That statement shows you know very little (nothing) about software development.
Swift reduces the time to create an app by nearly half, and reduces the complexity of the code. Swift code also runs faster than objective-c code, especially in math intensive functions. It also takes advantage of memory management functionality that is absent in Objective-C.
There is no way to "improve" Objective-C to make it equivalent to what Swift is today.
What is the point of say this? Imply that swift is not for fast apps?
For that, is necessary that Swift have a better support for non-Apple platforms. If I need to have something across many platforms is necessary to use a low-level lang like C/C++/Rust or a runtime like Java/.NET or similar.
This is certainly the biggest problem with swift, IMHO. I wish Apple get serious here and provide first class support for at least linux/windows of the core library:
https://www.reddit.com/r/swift/comments/8zb9y1/state_of_swift_for_androidlinuxwindows_on_2018/
----
Is important to note than instead of
The colossal mistake is C/C++. Both of them are massive bugs-friendly, security-impossible piece of languages that are behind almost all the problems of crashes, weird bugs and security problems for decades now. Costing billons not only in damages but in the amount of time and effort required to workaround them.
The problem is that all the OS today are on top of the "C ABI" ie: Eventually you need to lower your hopes to whatever C can do, not matter how problematic. However, is possible to reduce the surface area and use a better language, like Rust or Swift for most of the tasks and only lower to C for compatibility or to access the vast ecosystem around it.
Swift, like Rust and others, are far from a mistake. Is what is necessary to move the industry forward. Stay forever with C/C++ is like stay with Cobol, but worse.