Introducing Swift

Re:Introducing Swift by angersock on Monday June 02, 2014 @11:40PM (#7838014)

Suddenly Apple is doing something developers have been demanding from them for years and something lots of other companies like Google, Mozila and Microsoft has already done.

And yet they've decided to do it again, with yet another incompatible language! Joy of joys!

(And as for Java, it was my understanding that Apple had hobbled it by refusing to release updates on a timely basis.)

[ Parent | on HN ]

Re:Introducing Swift by toyg on Tuesday June 03, 2014 @03:20AM (#7838536)

> Apple had hobbled it by refusing to release updates on a timely basis.

I can see how they could get tired of being forced to ship almost-monthly updates just to support an extra language with very limited adoption. If you have to make that sort of effort, you'll probably do it for your native tools only (like Microsoft does with .Net). Besides, Java apps on OSX looked better than Java apps on Windows, but they were still recognizably different from Obj-C ones.

I wish somebody would write an OS in Python 3...

[ Parent | on HN ]

Re:Introducing Swift by jonhendry on Wednesday June 04, 2014 @03:57AM (#7844475)

"(And as for Java, it was my understanding that Apple had hobbled it by refusing to release updates on a timely basis.)"

That's a different, later issue.

Early on in the life of OS X, Apple offered a Java interface to the Cocoa class frameworks. In theory, you could write OS X applications using Java, calling into the Apple frameworks instead of using Swing or whatever Java frameworks.

This wasn't all that well supported, didn't perform well, and wasn't popular.

[ Parent | on HN ]

Re:Introducing Swift by mgkimsal on Tuesday June 03, 2014 @08:12AM (#7839592)

Sun should simply have hired some mac people and done it themselves. Entrusting the success of your entire company ( they changed their ticker symbol to JAVA!) to a 3rd party vendor's whims was and is silly.

[ Parent | on HN ]