Since it was a hidden setting that consumers (and presumably you) wouldn't have enabled, I don't think it will make any difference to you.
As a web developer too, I definitely disable cache. So this would affect me.
Since it was a hidden setting that consumers (and presumably you) wouldn't have enabled, I don't think it will make any difference to you.
No, this just altered the standardized testing for all laptops to improve Apple's results. Basically this is "you're holding it wrong" again. With that phone, holding it differently yielded better results. With this testing, changing a common testing parameter used with all laptops is going to yield a much better result...
As a web developer too, I definitely disable cache. So this would affect me.
Some people can't read...
According to Apple, it wasn't the caching setting itself that caused poor battery life, it was that the setting was triggering a bug which caused icons to constantly be reloading for no reason.
According to Apple, this bug is now fixed in the latest beta release. One would expect a new CR test that once again turns off caching to yield much better results this time.
It still doesn't fix the problem with the 2016 model having 1/3 smaller battery than the 2015 model.
No, it does not. When you visit MR or this forum, most of the files are coming from your local cache and you probably visit a lot of the same sites every day (search, blogs, news, facebook,...), so a lot of files these sites are using (images, javascript, css, fonts) are already in your cache.Disabling caching in a browser should not cause this type of battery drain. It simulates real world usage of a web browser.
I'm frustrated with myself for even glancing over here while eating lunch today. I no longer read the forums regularlyfor this reason.
Nonsense. The odd testing method caused a bug to be exposed. It's fixed now.. simple as that.
My MBP 13 gives me up to 3 hours of casual browsing and the odd youtube video with medium brightness. I guess I'm testing it wrong?
Apple says it isn't a setting used by most users. So, no web developers ever use Macbook Pro computers?
If it was indeed a bug, then the only response from Apple should have been, "We thank CR for testing our products so thoroughly. This high standard of testing has revealed a bug in Safari that would have affected many of our pro users. We have addressed this bug, and invite CR to retest our product, which we are confident will pass or exceed thier standards."
Well, it doesn't really speak for Consumer Reports that they didn't do additional testing. If it's a Safari setting, then an alternate battery life test with Chrome (very common use case) would've easily showed the anomaly in battery life. Why do they have so much credit anyway?
They explained this in the original article: "For the battery test, we download a series of 10 web pages sequentially, starting with the battery fully charged, and ending when the laptop shuts down. The web pages are stored on a server in our lab, and transmitted over a WiFi network set up specifically for this purpose. We conduct our battery tests using the computer’s default browser—Safari, in the case of the MacBook Pro laptops"For sure. Is my next door neighbor, who is a school teacher, going to 1) Turn on Developer settings, and then 2) Go to the setting to Disable Caches?
Why?
If that's your takeaway then I assume fixing the bug that Apple identified as the cause was wrong on their part?So Consumer Reports deceived all 7 of their readers by using a non-standard config and pretending like that was normal battery life.
I didn't much care for them before, now I know they post fraudulent results.
They explained this in the original article: "For the battery test, we download a series of 10 web pages sequentially, starting with the battery fully charged, and ending when the laptop shuts down. The web pages are stored on a server in our lab, and transmitted over a WiFi network set up specifically for this purpose. We conduct our battery tests using the computer’s default browser—Safari, in the case of the MacBook Pro laptops"
They want the pages to load fresh from their server as if coming from the interwebs. If the web pages are loading from Safari cache then their testing isn't consistent across all laptops. All previous macbooks have passed this exact same test with flying colors. The '16 MBP's had a bug in Safari that cause the erratic results, not CR's testing procedure.
Their testing has nothing to do with your neighbor, mine, me, or you. It's about consistency when testing all laptops.
Trust me. It's not. I have had the shocking 2006 model. I've had the kernel panicking GPU ridden 2008 model. I also had the image retention, screen peeling, pixel blowing 2012 model. I loved them all, but this is a huge step up for me and the smoothest first gen MacBook Pro I have used.
Although Apple fixed them all no questions asked (the 2012 one 4 times!), visits to the Genius Bar are hardly what I consider a Pro feature.
If it's a Safari setting, then an alternate battery life test with Chrome (very common use case) would've easily showed the anomaly in battery life.