[lynndylanhurley]

Here's a question - if the results were due to an obscure Safari bug, then why did Apple remove the battery life estimate with the latest OS X update?

I've been getting 2-3 hours max out of my new 15" 2016 MBP and I don't even use Safari. I'm just running webpack, vim and Chrome.

[caconym_]

I think they removed it because the battery life of the new MBPs has been getting a lot of negative attention, deserved or not, and in general people don't seem to be capable of understanding why the estimate would change for different workloads. Maybe the best PR move was just to remove it altogether. I wish they hadn't.

It's not the same machine, but I routinely get > 10 hours on my 2016 12" Macbook with a workflow that includes moderate to heavy browsing in Opera, coding in Tmux/Vim, and various compilers and interpreters invoked periodically. Have you had a look in Activity Monitor to see where all your power is going?

I'm using two non-Apple apps as the core of my workflow (Opera and Alacritty for terminal: https://github.com/jwilm/alacritty) but my battery life is still excellent. However, I chose them carefully on the basis of their efficiency. Things written in Javascript seem to be real resource hogs (Atom comes to mind), and Chrome is notorious for inefficiency in memory, at least.

[rrock]

Click on the battery icon in your menu bar, and see if there are any programs using "Significant Energy". Some programs will switch on the discrete graphics card without needing it, for example.

[acchow]

I'd suggest switching to Safari. I easily doubled my battery life while on El Capitan doing that.

Sierra has wrecked my battery life tho...

[pat2man]

Chrome is pretty bad for battery life.