3 ms·
Where 'throttled' means just as good as before. Occam's razor suggests that they simply hadn't finished the integration work before the ship date.
by rbarooah 16y ago
Where 'throttled' means just as good as before.
Occam's razor suggests that they simply hadn't finished the integration work before the ship date.
- SigmundA 16y agoExactly, UIWebView simply wasn't updated with the latest WebKit engine the Safari app is running. Web Clips use a special app wrapper that uses UIWebView, that is all. This affects real apps that use UIWebView to display HTML content, which is a lot of apps, including probably some of Apples own apps. You would think UIWebView would share the same WebKit with Safari, but Apple didn't do this, I doubt their reason are nefarious, probably just allows them to try new stuff out in the browser while being more conservative for the developer component.
- dunham 16y agoI think it's the same UIWebKit. If you're willing to Jailbreak your device, you could take a look at the files and find out. The issue is that no apps other than MobileSafari can do JIT compilation, due to security constraints put in place by the kernel. You can't write to a segment of memory and later make it executable. To pull this off with MobileSafari, I suspect that Apple put a back door in the kernel, and requires apps to be signed with a specific entitlement to get access to it. And I'm guessing that MobileSafari is the only app with this permission. For full screen web clips, it might be possible for Apple to give the wrapper the right permissions without breaking their security model. Hopefully they do this in the future. But I doubt that 3rd party native apps will ever be given the ability to modify code.
- semanticist 16y agoSorry, managed to down vote instead of up vote - all the talk of Apple trying to force people to make native apps is ignoring the key technical details you mentioned.