Earlier quoted context omitted.
Yeah, UIKit and SpriteKit will never come to other platforms. They constitute part of iOS' and macOS' competitive advantage. Swift's progress also has little to bear on that front as UIKit and SpriteKit are written in C, Objective-C, and C++; their use in Swift depends on Apple's Objective-C runtime which is not released as part of the non-macOS/iOS port of Swift for Linux.
To be fair, libobjc is open-source: https://opensource.apple.com/source/objc4/objc4-750.1/
Swift 5 Release Notes for Xcode 10.2
21–25 of 25 posts
Re: Swift 5 Release Notes for Xcode 10.2
#22Earlier quoted context omitted.
To be fair, libobjc is open-source: https://opensource.apple.com/source/objc4/objc4-750.1/
That is a very tiny part of Objective-C story.
Re: Swift 5 Release Notes for Xcode 10.2
#23Earlier quoted context omitted.
the point of using swift is to be faster than Python. if your computations are using numpy and most of your time is spent in these computations, passing through the python interpreter every time, it's going to have performance similar Python
> the point of using swift is to be faster than Python There are plenty of other compelling reasons to prefer Swift over Python such as its type system or its easy, somewhat native, integration with existing Swift, Objective-C, and C frameworks available for macOS, iOS, watchOS, and tvOS. Speed isn't the only driver, and I'm sure not it's not "the [only] point".
Re: Swift 5 Release Notes for Xcode 10.2
#24As someone who hasn't yet put in the time with swift, i get the sense that every version release of Swift includes a surprising amount of breaking changes. Are these edge cases that don't really effect anyone or does every Swift project you undertake basically cement itself into a swift version?