The point isn't with the fact that there is an issue, its that Apple is seemingly trying to sweep it under the rug.
The point isn't with the fact that there is an issue, its that Apple is seemingly trying to sweep it under the rug.
> The point isn't with the fact that there is an issue, its that Apple is seemingly trying to sweep it under the rug.
I think you missed the whole point of OP post: That is exactly what Apple has a reputation for doing. For example: The Antenna Fiasco -
http://www.engadget.com/2010/06/24/apple-responds-over-iphon...
I don't think that's quite it. Apple realises there's a problem, and that's why they have the standardised test. I think the real problem here is that Apple's test is insufficient, but they don't know that, so they don't believe their customers when they say they're having still having issues. And that's not reassuring for someone who's just spent a lot of money on a new machine.
Personally, I've never had this issue with my rMBP, but I'm sympathetic with those that do.
I personally can't see how they could not know, this is not the kind of issue where ppl are going to be blowing there whistle for no reason. So Apple knows there is an issue, if there own tests do not match the numbers of complains(to some degree) even more red flags should be going up.
I am no conspiracy theorist, but there seems to be some valid points in the article.
>I remember an Apple that bent over backwards to understand its customers’ point of view and stretched itself to meet the high expectations it sets.
Apple has always bent over to resolve issues for customers if they acknowledge the issue. For example, I had a pre-unibody MBP that the power button pushed through the top case. Apple very promptly took it back, replaced the top case and a few other cosmetic dings I hadn't complained about, and got it back to me.
On the other hand, Apple also has a long history of refusing to acknowledge some issues and giving the customer the run around on them, which is the type of complaint in this article.