Everyone says Chrome devastates Mac battery life, but does it? 36 hour test

Original Article ↗ Hacker News Discussion ↗

Claims that Chrome devastates MacBook battery life are challenged by a 36‑hour test suggesting Chrome and Safari now draw similar power under controlled workloads. Commenters debate how representative the test is—pointing to heavy use of YouTube and Google Docs, browser extensions, and battery-percentage measurements—as well as the impact of OS‑specific optimizations that Safari can exploit and cross‑platform engines often don’t. The thread broadens into concerns about modern web bloat, differing browser usage patterns (including Firefox and alternative Chromium-based browsers), and how vendor behavior and standards creep affect both performance and user choice.

Overall view on Chrome vs Safari battery use

  • Many are surprised Chrome did as well as (or better than) Safari in the test, challenging the long‑held “Chrome kills Mac battery” belief.
  • Some argue Chrome really did consume more power years ago and has since improved; others say that’s unproven and the belief may always have been anecdotal.
  • Several note that modern Mac laptop battery life is so strong that small browser deltas are practically invisible in daily use.

Impact of workload, sites, and extensions

  • Commenters stress results are highly workload‑dependent: heavy web apps, number of tabs, and background processes all matter.
  • Extensions are a major variable:
    • Content blockers (e.g., uBlock Origin) can reduce CPU, network, and GPU load overall, but they also add per‑request and DOM‑hooking overhead and can depress benchmarks.
    • Other add‑ons and “privacy hardening” can clearly slow pages and drain more power.
  • Some want Firefox and other browsers included, especially under multi‑tab, multi‑app “real work” conditions.

Test design and validity

  • Critiques focus on:
    • Heavy reliance on Google properties (Docs, YouTube) that might be optimized for Chrome or intentionally suboptimal elsewhere.
    • Dominance of long YouTube playback, which may skew toward Chrome and may not reflect everyone’s usage patterns.
    • Reliance on macOS battery percentage rather than full 100‑to‑0% discharge cycles per browser.
  • Others defend the test as a reasonable, if limited, real‑world sample and like that browser order was alternated to reduce bias.

YouTube representativeness debate

  • One camp says any “representative” web battery test must include YouTube, given its huge share of overall usage.
  • Another points out many people rarely watch YouTube on laptops, or prefer text content, so such a workload misrepresents their reality.
  • Some suggest adding or swapping in Netflix, other streaming services, or enterprise web apps.

Engines, OS APIs, and web direction

  • Discussion touches on platform‑specific graphics APIs (e.g., Core Animation, DirectComposition) and how native integration can significantly improve power efficiency versus cross‑platform layers.
  • Broader critiques target web “scope creep,” JavaScript‑heavy sites, and browsers evolving into quasi‑OSes, which many see as a core reason any browser drains batteries.