This sounds useful. Here are links that actually load on my phone.<p>- <a href="https://github.com/swiftlang/swift-java">https://github.com/swiftlang/swift-java</a><p>- <a href="https://forums.swift.org/t/improving-swift-support-and-interoperability-experience-for-android/71470" rel="nofollow">https://forums.swift.org/t/improving-swift-support-and-inter...</a>
Cool! One thing Swift is really (maybe uniquely?) strong at is C/C++/Objective-C interop, including mixing "legacy" code with Swift and even replacing it file-by-file with minimal ceremony. Looks like this is aiming to bring a similar level of interop to Swift<->Java.
Plus ça change: <a href="https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/Legacy/JavaBridge/JavaBridge.pdf" rel="nofollow">https://developer.apple.com/library/archive/documentation/Co...</a>
PythonKit (from Swift) is underrated but immensely useful in certain scenarios (i.e.: <a href="https://engineering.drawthings.ai/from-iphone-ipad-to-mac-enabling-rapid-local-deployment-of-sd3-medium-with-s4nnc-324bd5e81cd5" rel="nofollow">https://engineering.drawthings.ai/from-iphone-ipad-to-mac-en...</a>).<p>Hopefully JavaKit can find their usefulness too!
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.<p>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.<p>[1] <a href="https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/Legacy/JavaBridge/JavaBridge.pdf" rel="nofollow">https://developer.apple.com/library/archive/documentation/Co...</a>