4 ms·
Summary of what I can make out so far: * Write JS as usual. Write React as usual, but don't use the DOM JSX elements (or the React.DOM) factories - instead use
by sudhirj 12y ago
Summary of what I can make out so far:
* Write JS as usual. Write React as usual, but don't use the DOM JSX elements (or the React.DOM) factories - instead use the new 'NativeView' elements.
* The code you write runs in a Javascript interpreter on the background thread.
* The NativeView elements communicate transparently with a native server running on the main thread, which renders and fills native views based on the instructions sent.
* The JS runs react the usual way - I'm assuming the tree reconciliation happens the same way as well - the diff instructions are just sent to the native view server.
- binocarlos 12y agoNice summary thanks :-)
- devgeeks 12y agoHas anyone asked if this can use other JS libs other than just React ones? Also, if it's just using say JavaScriptCore and rendering native, I assume this means speed limitations imposed by the lack of Nitro/etc on the UIWebView are moot?
- danabramov 12y agoJSC doesn't have JIT. They claim perf is fine though (e.g. because render is always async, app code is always in background). We shall see!