News for hackers. Stuff that matters.
Re:Why the Nitro JavaScript Engine Isn’t Available to Other ... by kenjackson on Thursday March 17, 2011 @08:58PM (#2338866)
A way around this is to move the JIT to the kernel or to a different process. I would guess that that would hinder performance so much that, in typical usage, JIT-ting becomes too expensive to speed up things

Having the hosted browser in a different process shouldn't be too expensive. That's what Chrome and IE do. When you open up a UIWebView and process gets spun up that hosts the JIT (amongst the other plubming for the browser) and the host just has a window where the rendering takes place. This also fixes a whole host of other security problems hosting a browser in process.

Re:Why the Nitro JavaScript Engine Isn’t Available to Other ... by Someone on Friday March 18, 2011 @02:51AM (#2339636)
Chrome and IE run on systems with faster processors and Gigabytes of RAM. RAM, especially is tight on iOS devices.

I also guess that some iOS apps will want to overlay stuff on their web views, postprocess the data, register callbacks, etc. Supporting such use might be a bit of work that Apple hasn't done yet.