News for hackers. Stuff that matters.
Re:Open-sourcing Chrome on iOS by autoconfig on Tuesday January 31, 2017 @10:55PM (#13538088)
Your argument is still not making much sense. I don't see how the power efficiency of the APIs is relevant. The point is that they currently allow tons of applications (E.g. Candy Crush) that drains the battery. What's the reason for making the browser a special case? It's just rendering to the screen like any other application.

One argument I could see being made is that the browser is used more than others and thus warrants tighter control. But even that is weak. People are draining their batteries all day long playing games as it is.

Re:Open-sourcing Chrome on iOS by griffinmb on Tuesday January 31, 2017 @11:36PM (#13538286)
I believe that the real reason is that Webkit needs privileged APIs and unique executable memory regions for the jit. Giving third-party developers that access would make jailbreaking a simpler process.
Re:Open-sourcing Chrome on iOS by quesera on Wednesday February 01, 2017 @12:26AM (#13538512)
Anything that makes jailbreaking simpler also makes it easier for the device and data to be compromised.

Apple might have walled garden motives, but the security story is compelling on its own.