status-im/react-native
2
0
Fork 0
mirror of https://github.com/status-im/react-native.git synced 2025-01-17 21:11:45 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #806 from Rudimental/patch-4

Browse Source 
Update JavaScriptEnvironment.md
This commit is contained in:
Ben Alpert 2015-04-10 19:42:36 -07:00
commit b65d82d6e4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/JavaScriptEnvironment.md
View File

@ -12,7 +12,7 @@ next: activityindicatorios
When using React Native, you're going to be running your JavaScript code in two environments:
* In the simulator and on the phone: [JavaScriptCore](http://trac.webkit.org/wiki/JavaScriptCore) which is the JavaScript engine that powers Safari and web views. Due to the absence of writable executable memory in iOS apps, it doesn't run with JIT.
* When using Chrome debugging, it runs all the JavaScript code within Chrome itself and communicate 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 Objective-C 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.