zlacker

[parent] [thread] 2 comments
1. asddub+(OP)[view] [source] 2022-06-22 12:47:51
battery life is another stated reason I believe.
replies(2): >>kitsun+my >>noduer+Zql
2. kitsun+my[view] [source] 2022-06-22 15:40:46
>>asddub+(OP)
It’s a big one. Google and Mozilla don’t prioritize efficiency, and it shows in the difference in battery life between using Safari and Chrome or Firefox on macOS.

While users can choose their primary browser, they have no control over what embedded browsers third party apps use, and so if embedding Chromium becomes popular in third party apps it will unavoidably cut the battery life of many if not most users.

When/if Apple starts allowing third party engines on iOS, I think they should require engines to meet minimum efficiency levels to prevent this issue. As a bonus, it’ll allow savvy laptop users to use community builds of desktop Chromium/Firefox with iOS efficiency compliance flags switched on if they want to extend the battery lives of their laptops by an hour or two.

3. noduer+Zql[view] [source] 2022-06-29 08:38:23
>>asddub+(OP)
I can slip one line of code into a modern website that'll target a particular iphone model and run its battery to nothing in half an hour, and probably crash safari as well. Any language is susceptible to badly written or malicious code. At least with Flash it was in a box, in a virtual machine, and you had to approve it and could kill it at any time.
[go to top]