3 ms·
They probably just forgot to rebuild the WebKit view built into the Springboard that runs homescreen webapps with the new JS engine. I am sure they will issue a
by bengl3rt 16y ago
They probably just forgot to rebuild the WebKit view built into the Springboard that runs homescreen webapps with the new JS engine. I am sure they will issue an update soon.
- grayrest 16y agoI'd prefer to give them the benefit of the doubt, but this after breaking the web application cache for homescreen items in iOS 4.2 is a disturbing trend.
- bengl3rt 16y agoWell, I'll grant them that regressions occur during software development. However, it's highly unlikely they are unaware of these problems, they just deprioritize fixing them instead of things that affect their precious curated native apps.
- webXL 16y agoIs it possible that with multi-tasking, having two threads of the new Nitro JS engine open in memory slows everything down? It's not that big of a deal with 512mb of RAM and dual core, but the iPad 1 could be sluggish. I guess it's possible they only use one JS thread for everything (even the 9 "tabs" in Safari), and this really is just a bug.
- ryanpetrich 16y agoThere's one web thread per process (and JavaScript can either run on it or the main thread), but home screen apps run in their own process. Nitro doesn't use substantially more memory than the earlier engine.
- rahoulb 16y agoIn another thread discussing this there was the suggestion that Nitro's JIT compiler may need special privileges to mark writable memory as executable as iOS doesn't allow that under normal circumstances. Maybe that flag's been set for MobileSafari but not set for Springboard.
- recoiledsnake 16y agoApple forgot? With their so called obsessive attention to detail, that's hard to fathom. If this was about performance in native games, they would've rushed out a patch by now.