Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Swift/Java interoperability tools and libraries

twitter.com

Post reply on HN
Print view View original

11–20 of 23 posts

Re: Swift/Java interoperability tools and libraries

#11

Post by fidotron »

wiseowise wrote: post #5

Will be wildly ironic if Apple pulls uno reverse card and eats Kotlin on Android instead of the other way around.

This would happen in about five minutes if a SwiftUI port was included.

Which ironically would be just like Flutter, totally bypassing any native UI.

My gut feeling is both teams probably have a plan for steamrollering the other in the event of anti monopoly measures forcing each to accept the other store. I.e. it is conceivable you could launch the Play Store on iOS and run a significant proportion of Android apps through a compat layer.

Re: Swift/Java interoperability tools and libraries

#12

Post by jwells89 »

wiseowise wrote: post #5

Will be wildly ironic if Apple pulls uno reverse card and eats Kotlin on Android instead of the other way around.

If Swift were practical to use for Android app development, I would absolutely do so. I enjoy writing Swift more than I do Kotlin by a good measure and not having to wrestle with gradle and proguard would be a nice bonus.

Re: Swift/Java interoperability tools and libraries

#13

Post by koito17 »

This gives me flashbacks to the Objective-C / Java bridge [1] from over a decade ago. It makes me wonder how they are dealing with memory management when Java objects are being used from Swift (or Swift objects from Java). This was one (of various) issues that made using the Cocoa Java bridge a bit unpleasant.

I guess Swift has a lot less run-time dynamism going on, so it may not be too hard to translate Swift semantics to Java. Definitely interested to see how this unfolds over the next year.

[1] https://developer.apple.com/library/archive/documentation/Co...

Re: Swift/Java interoperability tools and libraries

#15

Post by favorited »

koito17 wrote: post #13

This gives me flashbacks to the Objective-C / Java bridge [1] from over a decade ago. It makes me wonder how they are dealing with memory management when Java objects are being used from Swift (or Swift objects from Java). This was one (of various) issues that made using the Cocoa Java bridge a bit unpleasant. I guess Swift has a lot less run-time dynamism going on, so it may not be too hard to translate Swift semant…

> It makes me wonder how they are dealing with memory management when Java objects are being used from Swift

It uses Swift macros to add a `JavaObjectHolder` property to Swift types annotated with `@JavaClass`[0]. `JavaObjectHolder` is a Swift class that takes a global JNI reference to the Java object, and releases it when the holder is destroyed[1].

The result is that a codegen utility emits Swift structs[2] that wrap the JNI values, and the JNI glue code for method invocation is applied at compile-time when the macros are expanded.

[0] https://github.com/swiftlang/swift-java/blob/e7d7a217e37d49b...

[1] https://github.com/swiftlang/swift-java/blob/main/Sources/Ja...

[2] https://github.com/swiftlang/swift-java/blob/main/Sources/Ja...

Re: Swift/Java interoperability tools and libraries

#17

Post by lukeh »

koito17 wrote: post #13

This gives me flashbacks to the Objective-C / Java bridge [1] from over a decade ago. It makes me wonder how they are dealing with memory management when Java objects are being used from Swift (or Swift objects from Java). This was one (of various) issues that made using the Cocoa Java bridge a bit unpleasant. I guess Swift has a lot less run-time dynamism going on, so it may not be too hard to translate Swift semant…

IIRC, the ObjC/Java bridge was first done at NeXT for WebObjects around 1996... almost thirty years ago!

Re: Swift/Java interoperability tools and libraries

#19

Post by pjmlp »

aaronbrethorst wrote: post #3

Plus ça change: https://developer.apple.com/library/archive/documentation/Co...

The reasoning being different though, back then Apple wasn't sure Objective-C would take off among Mac OS developer crowd, used to Object Pascal and C++, Java support and its high integration with OS APIs was a kind of Plan B.

Objective-C was actually embraced by the community, only Java heads cared about the bridge, and it was eventually killed.

I feel it was a lost opportunity, but what do I know.

Re: Swift/Java interoperability tools and libraries

#20

Post by pjmlp »

Alupis wrote: post #9
wiseowise wrote: post #5

Will be wildly ironic if Apple pulls uno reverse card and eats Kotlin on Android instead of the other way around.

Outside of Apple's ecosystem, is anyone using Swift? Kotlin is growing in all areas, especially backend (being fully embraced by Spring/Spring Boot et al).

Spring embraces all JVM languages that can bring them new customers.
Post reply on HN