Facebook/react-native
1
0
Fork 0
mirror of https://github.com/facebook/react-native.git synced 2025-11-01 09:14:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add Android code to the 0.11-stable branch.

Browse Source 
Cherry-picked https://github.com/facebook/react-native/commit/42eb5464fd8a65ed84b799de5d4dc225349449be
This commit is contained in:
Martin Konicek
2015-09-14 15:35:58 +01:00
parent 77167b02ee
commit 7cc3ba99e0
569 changed files with 44654 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/JavaScriptEnvironment.md
+1 -1
View File
@@ -12,7 +12,7 @@ next: navigator-comparison
When using React Native, you're going to be running your JavaScript code in two environments:
* On iOS simulators and devices, Android emulators and devices React Native uses [JavaScriptCore](http://trac.webkit.org/wiki/JavaScriptCore) which is the JavaScript engine that powers Safari. On iOS JSC doesn't use JIT due to the absence of writable executable memory in iOS apps.
* When using Chrome debugging, it runs all the JavaScript code within Chrome itself and communicates with Objective-C via WebSocket. So you are using [V8](https://code.google.com/p/v8/).
* When using Chrome debugging, it runs all the JavaScript code within Chrome itself and communicates with native code via WebSocket. So you are using [V8](https://code.google.com/p/v8/).
While both environments are very similar, you may end up hitting some inconsistencies. We're likely going to experiment with other JS engines in the future, so it's best to avoid relying on specifics of any runtime.