> More recently, I read the argument that it’s so bad that Chrome running it’s Chromium engine ought not be allowed to exist on iPhones and iPads. The subtext is John Gruber's post 6 days ago, defending Apple's iOS lockdown: "Imagine — and this takes a lot of imagination — if Google actually shipped a version of Chrome for iOS, only for the EU, that used its own battery-eating rendering engine instead of using the en…
I didn't realize John Gruber had reached "cult leader" levels of apologism.
Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
41–50 of 112 posts
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#42Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#43this "test" sounds pretty useless, and to immediately try to extrapolate the small sample to an eight hour battery life, lol
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#44Earlier quoted context omitted.
G Docs, alright, maybe , but any web battery test that doesn't involve YouTube simply wouldn't be representative.
I’d argue we could replace YouTube with Netflix; or test with more than one streaming platform. > YouTube accounted for 8.5% of total TV viewing in May, while Netflix was a close second at 7.9%. https://www.forbes.com/sites/howardhomonoff/2023/06/28/summe...
Assuming that's true, I still don't think it matters that much.
I expect that a very large proportion of Netflix that's watched is watched on a smart TV. Much larger than the proportion of Youtube that's watched on a TV.
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#45Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#46I think it would be much more interesting to put together ~40 hours worth of testing similar to what the author did, then run it with Safari until the battery dies, charge the machine for X hours (where X is the amount of time the battery takes to report 100% plus some margin) then run it with Chrome until the battery dies. Repeat as many times as you think necessary.
That would take battery percentage remaining reporting out of any load bearing place, which I believe is absolutely necessary here.
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#47Earlier quoted context omitted.
For my use case, it's quite obvious what's draining the battery: addons. Every trick and feature meant to preserve privacy and to remove visual trash will significantly impact load times, responsiveness, and battery life. It's all worth it to me, but there's no doubt a web without tracking and ads would easily double my battery life.
Those extensions usually improve performance, no?
I'll gladly pay the 15 minutes of battery power spent on filtering out that trash.
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#48Earlier quoted context omitted.
The most serious problem with the web IMO the endless scope creep. Maybe, idk, set a clear goal, work towards it, and then just stop and consider the web "done"? I hate it so much that almost everything in the IT industry is a process . It's necessarily unending. No one is shipping finished products anymore. Everything is in eternal beta. The web standards are the most egregious example of this.
I think what we need is not an HTML6, but rather HTML4-ish and something separate . I want web pages and web apps to be distinguishable, and not have every newspaper article and blog post hosted inside of a heavyweight application framework that either breaks or re-implements all kinds of basic user agent functionality. Simple pages should be implemented in a simple, constrained technology stack and heavyweight web a…
I don't see people putting that genie back in the bottle. Not when there are so many designers that override the scrollbar for aesthetics.
For the record, I'm with you - I think it would be great if most websites ran on gopher 2.0 that used markdown for its syntax. I just don't think it'll happen.
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#49Earlier quoted context omitted.
G Docs, alright, maybe , but any web battery test that doesn't involve YouTube simply wouldn't be representative.
Representative for who? I haven't been longer than 15 minutes on YouTube - in total within the past 2 years. So certainly not representative for me.
"Representative for me" is incoherent. You're not a population; you don't have population statistics.
Re: Everyone says Chrome devastates Mac battery life, but does it? 36 hour test
#50Earlier quoted context omitted.
The most serious problem with the web IMO the endless scope creep. Maybe, idk, set a clear goal, work towards it, and then just stop and consider the web "done"? I hate it so much that almost everything in the IT industry is a process . It's necessarily unending. No one is shipping finished products anymore. Everything is in eternal beta. The web standards are the most egregious example of this.
I think what we need is not an HTML6, but rather HTML4-ish and something separate . I want web pages and web apps to be distinguishable, and not have every newspaper article and blog post hosted inside of a heavyweight application framework that either breaks or re-implements all kinds of basic user agent functionality. Simple pages should be implemented in a simple, constrained technology stack and heavyweight web a…