Linked by Thom Holwerda on Fri 18th Mar 2011 18:26 UTC
Apple The past few days have seen a stink regarding web applications on iOS. El Reg ran a story about how web applications launched from iOS' homescreen ran significantly slower than when ran inside mobile Safari. As more details emerged, it became clear this wasn't a deliberate move by Apple - but rather an implementation issue.
Permalink for comment 466867
To read all comments associated with this story, please click here.
Comment by Kroc
by Kroc on Sat 19th Mar 2011 08:33 UTC
Kroc
Member since:
2005-11-10

When Mozilla created first TraceMonkey, and then JaegerMonkey, they had to disable it for the JavaScript used in Firefox's chrome because that load of code was not programmed with JIT in mind since it used a wider set of APIs than vanilla JS and communicated with XPCOM components and C-interfaces. Firefox 4 now ships with it all switched on.

I see this as similar for the Apple situation. Running web code is one thing, but JavaScript used in WebUIViews in third party apps could be doing anything beyond the scope of typical JavaScript. What's more since JIT allows for a form of memory (of sorts), this could be used as a new, effective form of jailbreaking. Just add a web-page to your home screen and then run it -- the context changes because the code is no longer running inside Safari, but as its own app outside Safari.

We'll just have to wait and see what the next update from Apple does.

Reply Score: 1