[citation][nom]Cleeve[/nom]Yeah, no kidding, right?We totally could have published this weeks prior before there was a fix. Instead, we gave AMD the heads up and worked with them to remedy a problem that they appreciated being told about.Apparently, giving a shizz about image quality and looking into issues isn't OK with some commenters if AMD is involved because they'd rather we bury it.If it was Nvidia who had a problem, and we found it, none of those people would have complained.Pathetic. They know who they are, and they know it's true, too.[/citation]
Exactly. There's four ways it could've been done:
1) Run a headline as soon as you've found the problem informing everybody that there is a problem and that AMD are cheating
2) Run the same headline without the accusation
3) As 2, but promise to talk with AMD about it/say you're in contact with them
4) Hold the article back until AMD have gotten in touch and the issue has been, at the very least, acknowledged with a timeframe on a fix
1 is definitely wrong, 2 is a name-and-shame exercise and only a step up, 3 is a big improvement but it might not reduce the AMD bashing, and 4 is or should have been the best practice, instead we get a whole ton of comments along with more than the slightest hint of fanboyism.
I'm (apparently) one of the rare individuals on Toms who doesn't really experience AMD driver woes. That's okay, I am way off the bleeding edge (4830, rah!) and it wouldn't matter too much if things got a bit worse. However, historically, there have been plenty of complaints about driver quality and what makes it worse is that the hardware is usually excellent all-round. I remember the 8500 and the almost endless lamentations about how good it was compared to the NVIDIA competition, yet drivers were killing it before it could truly compete. We all know AMD (and, in the past, ATi) can make impressive cards, but the situation at times would be akin to buying a sports car with lousy engine mapping. Conversely, the same can happen with NVIDIA - the 196.75 drivers, from what I've read, play havoc with fan settings, causing a graphics card to potentially fry itself. Apparently, this isn't the only instance of this happening, but it does show that neither AMD nor NVIDIA is infallible.
All too often, people are happier to bitch about a problem and the respective company rather than actually sit down, diagnose and discuss the issue. At the risk of sounding like a Toms apologist, they have at least looked at issues, what might be the causes, and what could be done to fix or at least work around the problem at hand. If Toms wanted to slate AMD, I'm sure AMD would stop sending them review hardware, but you still have to offer constructive criticism otherwise you wouldn't have a bad word to say about anybody. Having a bad review can be just as good, if not better than, a good one, as you feel compelled to investigate why something did so badly. Toms, like other sites, readily heaps criticism on Intel's HD graphics (especially their drivers), yet Intel aren't suddenly going to stop sending review kits. Everybody slated Fermi for its power usage, yet NVIDIA didn't halt sending them cards. As it is, a single slightly misworded (or rather, should that be misread?) conclusion can send dozens of people into spouting accusations of favouritism.
So yes, sometimes there really is no way to avoid being slated for a thorough article which has actually benefitted an entire consumer group. 😛
I'd like to add that Toms occasionally goes above and beyond - I made full use of K10STAT thanks to the two-part Toms article on maximising efficiency with K8, K10 and K10.5 CPUs, and I'm sure a lot of people here use this or similar software to reduce power usage without reducing performance; after all, not everybody is an overclocker (certainly not here with a PII 710 on an AM2+ board).