Earlier quoted context omitted.
> people will figure that out and adapt for themselves No they won't. People on HN will. Not the average person. > Security-wise, the sandbox should limit damage to within the browser The problem is, arbitrary code execution vastly expands the risks. Your "should" is doing all the work there. > Standardization, eh? Forcing Safari on iOS and not making it available on the mass market platforms Huh? Apple follows web s…
>> people will figure that out and adapt for themselves >No they won't. People on HN will. Not the average person. Yes they will, Apple has made it very easy to see. To check iOS app power usage, go to Settings > Battery, where you'll see a breakdown of battery consumption by app for the last 24 hours or 10 days, showing usage time and background activity, allowing you to identify power-hungry apps and manage setting…
And what percentage of users do you think ever check that, or even know it's there to check?
> If that's a problem for web browsers, then it's a problem for every single app in the app store.
No it's not, the app store disallows arbitrary code execution.
> There's nothing really unique about a web browser app that makes it more risky than any other app.
Yes there is -- JavaScript.
> Javascript is already very much sandboxed.
...by Safari. It wouldn't be if you allowed any developer to write their own JavaScript interpreter as part of their own browser.
> If web standards are standards, then let other web browsers on iOS.
That's a non-sequitur.