News for hackers. Stuff that matters.
Re:Inside Swift by agentcoops on Wednesday June 11, 2014 @12:20AM (#7876497)
"Swift is Apple’s new programming language, said by many to ‘replace’ Objective-C. This is not the case. I’ve spent some time reverse engineering Swift binaries and the runtime, and I’ve found out quite a bit about it."

Correct me if I'm wrong (and my point certainly isn't meant to detract from the interest of looking more in-depth at Swift internals), but this article doesn't appear to support this claim at all. It seems equivalent to saying Scala isn't meant to replace Java, or C assembly, because at the end of compilation it's all just Java. Abstraction is real. Also, Apple is providing a "migration guide" for porting Objective-C apps over to Swift. Nothing is conclusive, obviously, but certainly the article does not show that Apple doesn't intend for Swift to ultimately replace Objective-C as the primary language of Mac development.

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.