4 ms·
Interestingly, they seem to be using JavaScriptCore instead of V8 as their JavaScript interpreter: https://github.com/facebook/react-native/blob/42eb5464fd8a65e
by nolanl 11y ago
Interestingly, they seem to be using JavaScriptCore instead of V8 as their JavaScript interpreter: https://github.com/facebook/react-native/blob/42eb5464fd8a65ed84b799de5d4dc225349449be/ReactAndroid/src/main/jni/react/JSCExecutor.cpp https://github.com/facebook/react-native/blob/42eb5464fd8a65...
- bsimpson 11y agoAs I recall, they announced that alongside React Native in January. I believe it was to avoid subtle differences between the JS executed on various platforms (e.g. to prevent a component from using a feature supported in V8 but not JSC).
- kzzzf 11y agoThere are a bunch of other benefits of this, e.g. we use same API on both platforms to hook up profiling. We definitely want to experiment with other JS VMs in the future though.
- vjeux 11y agoWe designed React Native to run with any JS engine: jsc, v8, (wk)webview, inside of Chrome/Safari/Firefox, inside of Node, ... We released it with JSC today mostly for convenience: we had JSC setup from iOS and it works. But we're open to ship with a different engine if there are performance benefits.