Hacker News Reader

My previous phone - an HTC one m7 - had some battery issues when it was pretty new. I limited myself to something like 2 or 3gb per month on cellular data (because that was my plan) and yet I still had to charge my phone at work somedays. (It's not about battery over the whole month - it's about the worst case on any given day.)

I learned to debug by looking at the system data usage monitors - the standard power usage per app wasn't helpful. Turned out the problem was just a data hungry photo app we were developing at the time. We made it nicer on data usage before we launched.

And after all that, chrome was usually in my top 3 apps for data usage. Probably still is. So they absolutely should be optimizing it.

Granted that was several years ago but in some parts of the world that phone would probably be better then what the average consumer uses today.

> Their own customers

Can you explain what you mean? Chrome does not have any customers.

> And what delicious irony if they couldn't solve this with HTTP/2 because of servers not implementing the spec correctly or having weird undocumented quirks (their reason for not enabling pipelining despite it working just fine).

How do you envison the browser to solve this when the server is not H2 capable?

Who are their customers?