4 ms·
You seem to be missing a few things: - data usage is correlated with battery usage, which is important on mobile - the http2 prioritization point is only half
by dgoldstein0 8y ago
You seem to be missing a few things:
- data usage is correlated with battery usage, which is important on mobile
- the http2 prioritization point is only half valid. Two big assumptions that probably don't hold in practice: whether the implementations actually implement priority correctly, all the way through the stack (e.g. perhaps some servers have a suboptimal implementation?), And whether having a bazillion low priority image requests can hit some slowness - e.g. I would expect there to be some limit on how many streams http2 implementations will allow simultaneously. And lastly, http2 is based on tcp so even if the prioritization is good, changing the priorities as the user scrolls means that the bytes currently transferring are likely less important and holding up the more important response - which is probably not a big deal on a good network but with any amount of packet loss will introduce lots of extra delay.
- bsdetector 8y agoTheir own customers are using less than 15 GB per month, how much battery could they possibly save on the radio? A single video will use more radio time than days of image downloads in the browser. Furthermore, Google themselves didn't mention battery savings but just fewer bytes sent. 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).
- mda 8y agoWho are their customers?
- dgoldstein0 8y agoMy 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.
- eh78ssxv2f 8y ago> 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?