Re:Tragedy of the WebKit Commons
by MatthewPhillips on Wednesday February 13, 2013 @11:22PM
(#5217703)
Mobile Safari is only updated once a year.
Which is a very different thing to say than "UIWebView is an older implementation". Especially when you're talking about removing something from jQuery that was meant for older versions of WebKit only to have to put it back when you discover that, shockingly, there exist browsers out there that aren't on the bleeding edge of WebKit!
Not everybody runs Chrome.
Nope, it's usually updated with every single minor and security release as well.
Re:Tragedy of the WebKit Commons
by MatthewPhillips on Wednesday February 13, 2013 @11:33PM
(#5217748)
Only receives new features once a year. Safari (mobile or desktop) isn't exactly a model for rapid releases. It's missing a lot of stuff that Chrome has had for months, sometimes years.
UIWebView is precisely the same WebKit that powers MobileSafari, which is typically kept in sync with WebKit for the corresponding OS X release (so iOS 6.0 and Mac OS X 10.8 have roughly equivalent WebKits).
Pretty much the only difference between UIWebView and MobileSafari is the fact that MobileSafari runs JavaScript faster (by virtue of being allowed to mprotect pages, which almost no other app on the system, including 3rd-party apps, are allowed to do). But aside from a speed difference in JS execution, UIWebView is the same WebKit that's used in MobileSafari.