The haters will still hate. This is far and away the best Mac ever made. I've owned tons of them and this is definitely the best. I'm on my Mac all day as a programmer.
[doublepost=1484275126][/doublepost]
Read their report.
[doublepost=1484275291][/doublepost]
A bug was triggered when the browser was in the no cached state. Apple fixed that bug. The bug could be virtually anything. You would have to look at their source code to figure out the actual cause.
Now we need a consumer reports for consumer reports.
They never get into specifics.WHat was that bug? I dont need to look at the source code... It's common for the fixes to be included in the release notes
Parents?Even more interesting is getting battery life times of 12, 14, 16, 18 1/2, and 19 1/2 hours in some trials under a test procedure that's much more rigorous than Apple's, where Apple's published spec was up to 10 hours of battery lifetime.
Makes me wonder if CR actually did any kind of observation, monitoring, and supervision in their test protocols.
This is why some, more likely engineers, have little respect for CR's test procedures.
There may not be any info until macOS 10.12.3 is releasedWHat was that bug? I dont need to look at the source code... It's common for the fixes to be included in the release notes
CR is complete class. Wish there were more independent testing companies instead of all the sponsored crap reviews that pollute the 'net.
How about a little less Hatorade?Whaha!
Why recommend a company with enforced-only escalation anyway...
The truth is this test is far more lenient than Apple's test. They set the screen at 100 nits which is nearly a quarter the brightness that Apple says they test at. Modern hardware is so efficient at browsing that one of the main power draws in this test is the screen. This result is not that surprising.Even more interesting is getting battery life times of 12, 14, 16, 18 1/2, and 19 1/2 hours in some trials under a test procedure that's much more rigorous than Apple's, where Apple's published spec was up to 10 hours of battery lifetime.
Makes me wonder if CR actually did any kind of observation, monitoring, and supervision in their test protocols.
This is why some, more likely engineers, have little respect for CR's test procedures.
Well, this isn't my experience. And I'm betting that, as per usual, it isn't the experience of most typical users either. (They're the majority who are out happily using their computers, and not needing to post negative comments and reviews on tech-blogs...)if you don't get 15 hours you are using the 'wrong' way.
You are supposed to use it like Tim Cook wants you to use:
1. don't go online
2. keep the screen brighteness at the minimum
3. take a 40 minute break every hour
4 don't use any app
then you 'may' be able to get 15 hours !
EasyI'll only believe it when the battery time indicator is back.
I think there might be another (hopefully!) SOFTWARE issue that is OCCASIONALLY doing something "inappropriate" with the dGPU. This is based on another MR poster who said that he "caught" his tbMBP 15 getting HOT right about where the GPU is located; but NOTHING was running that would explain the dGPU running, and I believe that it even reported that it was NOT using the dGPU.You're right. I think it has to be software related. I did a test of the physical battery like someone in another thread described the apple hotline did with him, with some terminal wizardry and have it run for over 15 hours.. it worked.
But as soon as I start using it in real life, it drains like NOTHING! It's really absurd after my 13 hours macbook air.
That is clearly not what he meant, and your argument is flawed. The first half of the second sentence is linked with the first sentence, but the second half is not.
I am not sure what this means? You mean the MacBooks or the nTB MacBook Pros?All the clowns who exchanged for the nTB MacBook...
You poor souls.
There are actually a few NON-Apple, Skylake-based laptops boasting similar run-times. IIRC, the 15" HP Spectre X360, which is a MBP-wannabe with about the same "thickness" and a similar W/h rating on the battery and a similar CPU, is one of them.It's a standard benchmark so they can compare one machine to another with a standardized workload. It's not some all encompassing test to reflect what you'll get with your usage.
Your post is a great example about how facts are bended through incompetent journalism and careless retelling by forum posters who didn't bother to read the entire story. Facts: CR was using a non-default, debugging configuration of Safari that can only be activated via a hidden developer menu. Virtually no users use that configuration. Yes, its Apple's bug in the end, but this bug only affects a very particular, low-profile operation mode and is therefore much less tested than the configuration a normal user would use. CR should know that using non-default settings of a browser cannot be representative for default operation. They have enabled that setting to emulate a particular scenario — and that made sense — however, they should have implemented that scenario at their server's end instead. Their mistake, one that I consider to be very crude for such a well-known organisation — is that they used a non-default configuration of the browser while not mentioning this fact in their original review(!!), observed some conflicting and overall clearly weird results (they even say it themselves!), and with all that, still proceeded to publish the article. I come from the scientific community, and thing like these are considered gross negligence and unprofessionalism. If you get non-systematic results in your experiment, which also conflicts with other related experiments, the only conclusion you can make is that your test is obviously not working properly.