This answer is a load of rubbish. Not only is it technically incorrect but there are no sources and yet it has a lot of upvotes. It is very difficult to disprove something that is so vague, the differences in firmware strategy, etc. happen over time, they arn't neccesarily apparent in benchmarks/noise tests.
How do we deal with people upvoting what they want to hear rather than what is correct?
People will always vote however they want, you can't apply any control to this - if the post is helpful to the person reading it, it is their prerogative whether they upvote it or not. With this in mind, your actual question should be:
Well, there are multiple ways to deal with a highly voted but incorrect answer!
A couple of things to note:
<date>/<patch>/<cake> before putting the updated information at the top of the answer, or you can post your own answer clearly stating that your information is valid as of <date>/<patch>/<cake>This has already been discussed extensively on Meta.StackOverflow.
Downvoting may not achieve much, because of a very simple reason: users who are most likely to arrive at that question's page are those less familiar with the topic (hence them seeking an answer). They're therefore quite likely to just upvote the top answer and run with it. Here's an example, an answer that has been wrong for 2+ years until I bugged a moderator enough, who in turn bugged the OP, who finally edited their answer.
I would contact the OP and ask them to edit the answer. If they don't, and there is solid agreement that the answer is wrong - be bold and edit it yourself. I cannot find any rule (such as not "drastically" changing the meaning) to ethically justify spreading factually incorrect knowledge.
