4 ms·
All good points. The big difference with the bridge going to Objective-C, though, is that I believe it is now possible to build a native UI by calling right fro
by apike 13y ago
All good points. The big difference with the bridge going to Objective-C, though, is that I believe it is now possible to build a native UI by calling right from JavaScript to Objective-C. Impact is interesting for games and canvas-like rendering, but what I'd love is to be able to build the models and controllers of a highly performant, native-UI iOS app using JavaScript and UIKit. Sort of like Appcelerator with a layer removed.
- nglevin 13y agoThat's fair. This does save one ugly, extra step that I didn't mention, which would be to call into the Objective-C runtime's C API [1] to dispatch messages and introspect Objective-C classes. Should make it easier for developers to build their own middleware platform without getting too deep into reams of C boilerplate. [1] - https://developer.apple.com/library/ios/#documentation/Cocoa/Reference/ObjCRuntimeRef/Reference/reference.html https://developer.apple.com/library/ios/#documentation/Cocoa...