Swift, the new way to build iOS Apps. Here's how

Re:Swift, the new way to build iOS Apps. Here's how by pjmlp on Tuesday June 03, 2014 @11:21AM (#7840708)

I remember Apple representatives promising to a room full of CERN researchers that the JavaBridge wasn't going away and how Java was a first class language for Mac OS X development.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by weegee101 on Tuesday June 03, 2014 @11:30AM (#7840774)

This is not even remotely similar to that situation. Obj-C is far more important & integrated than I think you realize.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by pjmlp on Tuesday June 03, 2014 @12:35PM (#7841197)

I know Objective-C since 1999, when I had to port some software from NeXT to Windows, so I do know a few things about it.

From my point of view, many will jump to Swift if given the chance.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by gress on Tuesday June 03, 2014 @03:00PM (#7842106)

You are misunderstanding - this isn't about which is better. Almost all new application code will be written in Swif, but swift doesn't bridge between C and the Swift/obj-c runtime, so Objective-C will continue to be required for writing the glue layer.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by pjmlp on Tuesday June 03, 2014 @03:52PM (#7842341)

Yes it does.

https://developer.apple.com/library/prerelease/ios/documenta...

Additionally, this is just version 1.0. So nothing rules out that if Apple sees the language being widely adopted, other improvements in the FFI area aren't made.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by gress on Tuesday June 03, 2014 @07:47PM (#7843349)

I stand corrected, and your argument holds, however there is a great deal of objective-c code out there, so it will take a long time to go away.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by weegee101 on Tuesday June 03, 2014 @01:44PM (#7841654)

Yes, and I think people should head to Swift if it fits their needs. That is very different from Objective-C losing support however. Objective-C is not going away.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by scott_karana on Tuesday June 03, 2014 @07:09PM (#7843240)

How many people actually wrote Cocoa apps in Java?

The only Java apps of the era that I remember used non-native UIs, and were painful.

Whereas I'd be shocked if Swift wasn't adopted wholesale by iOS developers.

[ Parent | on HN ]

Re:Swift, the new way to build iOS Apps. Here's how by pjmlp on Wednesday June 04, 2014 @02:59AM (#7844340)

This is not about the present.

Rather back when Mac OS X 10.0 was being released and Apple was unsure if developers would be willing to write Objective-C code.

They created their own JVM, with Objective-C runtime support (JavaBridge) and let the developers choose.

At the same time, Apple representatives did sessions at UNIX heavy user groups, like CERN, where they sold Mac OS X as a better BSD, and Java as first class language was part of the feature list.

As they saw developers were comfortable adopting Objective-C in their toolchains, the JavaBridge was dropped.

[ Parent | on HN ]