News for hackers. Stuff that matters.
Re:Safari Is Not the New IE, But… by mikeash on Wednesday August 19, 2015 @11:19AM (#10086055)
Mobile Safari also deserves hate because Apple prohibits all alternatives. You cannot ship a browser for iOS unless it uses Safari's engine. There's no technical reason, it's just a decree from Apple about what they'll allow.
Re:Safari Is Not the New IE, But… by mightykan on Wednesday August 19, 2015 @04:14PM (#10088143)
There is very much a technical reason that third-party rendering engines won’t work: JavaScript JIT. Basically, for JIT to work, a process has to be able to mark a piece of memory executable, which would cause all sorts of issues with sandboxing/security.

Apple did introduce XPC in iOS 8 and all the extensions use XPC extensively to respect the sandboxing rules. This is what they used to introduce the WebKitViewController whose JavaScript performance is on part Mobile Safari (UIWebView’s JavaScript performance is poor due to not having JIT). In fact, the new SafariViewController that was introduced in iOS 9, which is effectively an embedded Mobile Safari in third-party apps, is mainly possible because the OS has first-class support for XPC within the confines of the application sandbox.

I could see, although I’m not sure how likely it would be, Apple introducing a new Extension Point for rendering engines. Although it’s attractive to attribute malice to their intentions, I don’t think Apple are actively enforcing the “all third-party browsers have to use WebKit" for any other reason than security and battery life impact. If they could find a way to allow third-party rendering engines/browsers to work within the confines of the application sandbox, be secure and have insignificant impact on the battery life, they would allow it. They’re almost there technically, anyway.

Re:Safari Is Not the New IE, But… by mikeash on Wednesday August 19, 2015 @04:29PM (#10088215)
Since UIWebView doesn't do JIT, as you say, and third party browsers using UIWebView are allowed, I don't think this theory holds up. The inability for third-party engines to do JIT certainly is a problem, but it doesn't look like the problem that causes Apple to make this restriction.
Re:Safari Is Not the New IE, But… by xbmcuser on Wednesday August 19, 2015 @11:57AM (#10086403)
There is a technical reason other engines won't hamper or slow web apps. This will allow for apps on ios from outside the app store. That is the only reason they are not allowing other browser engines.
Re:Safari Is Not the New IE, But… by mikeash on Wednesday August 19, 2015 @12:04PM (#10086472)
How does Safari hamper or slow web apps?
Re:Safari Is Not the New IE, But… by bobajeff on Wednesday August 19, 2015 @12:04PM (#10086468)
If I remember correctly. That wasn't spelled out exactly. I think the policy that browser vendors are referring to is one that says something like "[no app can duplicate functionality that's in the OS]" or something to that effect.

Basically, no vendor wants to put in the work of porting to iOS without the guarantee that it can be excepted in the App Store.

Re:Safari Is Not the New IE, But… by mikeash on Wednesday August 19, 2015 @12:53PM (#10086803)
I'm not sure how it was in the past, but it's explicit now:

"2.17 Apps that browse the web must use the iOS WebKit framework and WebKit Javascript"

Re:Safari Is Not the New IE, But… by bobajeff on Wednesday August 19, 2015 @03:31PM (#10087843)
Oh, too bad about that.
Re:Safari Is Not the New IE, But… by koffiezet on Friday August 21, 2015 @09:41AM (#10097337)
I'm pretty sure Opera for iOS uses it's own renderer:

https://dev.opera.com/blog/opera-mini-8-for-ios/

Re:Safari Is Not the New IE, But… by mikeash on Friday August 21, 2015 @10:42AM (#10097774)
This is either a loophole due to the fact that rendering happens server-side, or Apple just hasn't bothered to smite them yet. The rules are extremely clear.