4 ms·
> Apple would had fix all the ongoing issues with the Java bridge I really don't think they could have given the non-dynamic nature of Java. That part missin
by protomyth 8y ago
> Apple would had fix all the ongoing issues with the Java bridge
I really don't think they could have given the non-dynamic nature of Java. That part missing from Java's semantics and execution model is pretty critical and would only be added to the JVM much, much later. I have to agree with cmiles about the "hacky" nature of the bridge.
- pjmlp 8y agoDynamic loading, interfaces, bundles, reflection was already there in those Java versions. The only things I can recall not being there aren't that well supported by Swift as well, regarding dynamic patching classes, missing method handling, swizzling and such.
- protomyth 8y agoCategories were missing and viewing all the challenges JRuby had to work through is a good start for the problems with trying to duplicate Objective-C functionality.
- pjmlp 8y agoYes, I forgot about categories. Regarding JRuby, most of the issues were related to translating Ruby code into JVM semantics. Doing FFI to external Objective-C is a bit different.