News for hackers. Stuff that matters.

A comment on A Faster Facebook for iOS. Parent comment

Re:A Faster Facebook for iOS by Xuzz on Thursday August 23, 2012 @02:40PM (#4424102)
No they can't: part of a process cannot create executable memory while another part cannot. They'd have to move WebKit completely out of process: a huge task as it already does most text drawing.
[ Parent | on HN ]
Re:A Faster Facebook for iOS by raganwald on Thursday August 23, 2012 @03:26PM (#4424381)
An interesting alternative would be to enhance the current 'Save to Home Page' feature beyond specifying a manifest of resources and a home page icon. If this was fattened up to allow developers to make something that looked even more like an app but was running Safari (not a UIWebkitView inside a native app), you might have something interesting.

Pure conjecture on my part.

[ Parent | on HN ]
Re:A Faster Facebook for iOS by hokkos on Thursday August 23, 2012 @03:12PM (#4424303)
A task that they are doing with http://trac.webkit.org/wiki/WebKit2
[ Parent | on HN ]
Re:A Faster Facebook for iOS by kalleboo on Thursday August 23, 2012 @10:55PM (#4425987)
Which is what Safari does on OS X.
[ Parent | on HN ]
Re:A Faster Facebook for iOS by MatthewPhillips on Thursday August 23, 2012 @02:49PM (#4424159)
> They'd have to move WebKit completely out of process

Then that's what they need to do, JIT is a requirement for fast JavaScript and 2012 JS speeds cannot be the end of the line.

[ Parent | on HN ]