<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>tlrobinson</author><text>AFAIK the only way Apple can enable Nitro for 3rd party apps without enabling executable memory pages generally is by separating JavaScriptCore (and WebKit render engine) into separate processes (ala WebKit2 / Chrome) which are allowed to create executable memory pages.&lt;p&gt;Then, of course, there is no way to create bindings between your code and the JavaScript interpreter (at least not without the overhead of IPC, which would probably negate any benefits of enabling Nitro).&lt;p&gt;So yeah, I wouldn&apos;t hold my breath.</text><parent_chain></parent_chain></comment><story><title>IOS games using JavaScriptCore without WebKit</title><url>http://www.phoboslab.org/log/2011/04/ios-and-javascript-for-real-this-time</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jonbro</author><text>I am super glad he has released this. He is not joking about compiling javascript core for iOS being painful, I dumped many hours into it. It would have been nice of him to release the project files just for jsc under MIT or something, but I guess people have to make money somehow.</text><parent_chain></parent_chain></comment><story><title>IOS games using JavaScriptCore without WebKit</title><url>http://www.phoboslab.org/log/2011/04/ios-and-javascript-for-real-this-time</url></story>