On Aug 18, 2015, at 15:48 , Charles Srstka <[email protected]> wrote: > > Currently, the Swift runtime hasn’t stabilized yet, and it’s pretty unlikely > that any system frameworks will be written in it until it is.
The bigger issue, I think, is that apps using Cocoa APIs have to continue to run against existing Cocoa frameworks. If this means that Cocoa frameworks can’t be modularized/namespaced, then there’ll never be a solution to Richard’s “context” problem. Note that the above statement doesn’t mention language at all. It’s an ABI compatibility problem, and I was apparently too naive in hoping that the advent of Swift would bring a solution to that problem. On Aug 18, 2015, at 15:19 , Quincey Morris <[email protected]> wrote: > > Actually, I did look, but obviously I did not see. This is the second time in a week I’ve looked at code and failed to distinguish which language it was written in. This is a little worrying. Are we going to have to have public service announcements for developers converting to Swift? (“This is your brain. This is your brain on Swift.”) _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
