News for hackers. Stuff that matters.
Re:Inside Swift by gilgoomesh on Wednesday June 11, 2014 @12:46AM (#7876549)
Yeah, the article's technical analysis is good but I'm not sure what this line was supposed to say: what it actually says is wrong. Swift is definitely intended to replace Objective-C.

Perhaps that line in article meant that it's not binary identical to Objective-C. Swift classes definitely use different method invocation semantics (unless you adorn the class with the @objc attribute).

Re:Inside Swift by eswick on Wednesday June 11, 2014 @01:47AM (#7876630)
What I meant by that was, the Objective-C runtime is still needed.
Re:Inside Swift by pjmlp on Wednesday June 11, 2014 @03:01AM (#7876775)
Sure, because Apple wants a transition path for existing code.

The Objective-C runtime takes the role of COM in Mac OS X/iOS.

A binary ABI between OO languages.