From da3b982abef1c2cdee31bf6da057cfdee6d2a4ad Mon Sep 17 00:00:00 2001 From: David Rabkin Date: Fri, 10 Apr 2015 19:18:04 -0700 Subject: [PATCH] Update JavaScriptEnvironment.md -fix grammar in a sentence --- docs/JavaScriptEnvironment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/JavaScriptEnvironment.md b/docs/JavaScriptEnvironment.md index a2bca7ea2..cccf3800e 100644 --- a/docs/JavaScriptEnvironment.md +++ b/docs/JavaScriptEnvironment.md @@ -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.