The real issue that I see is: why did you see a 2 month old crap question???
This was a systemic failure, many things went wrong in a house-of-cards tumble-down mode that got you to look at this junk. Roughly like this:
The question was ignored back in April; the mangled title was probably enough to keep SO users from looking at it. Systemic failure: the SO engine accepted a question and never noticed simple capitalization mistakes like the lower-case 'i'** and a question body that was too short and filled with spelling errors.
The question got a crap answer from a low-rep user. Just a link to a MSDN article. Systemic failure: the answer was accepted even though 50% of it was a just link soup and exactly matched a comment posted to the question. The user that posted the answer has a large number of downvotes. No sign that it was ever reviewed by anybody.
The answer got an upvote, even though it was worthless. Systemic failure: users from Southern Asia regularly get upvotes for no conceivable reason. The user's rep history has standard evidence of getting serial upvotes (3/25/11). They did not get detected, a very common mishap these days.
The question went dormant for two months, well on its way into the belly-lint of SO and being forgotten like it should be. Systemic failure: the SO engine today thought it was Really Important for you to have a look at it. There were about 90 questions tagged [c] today, yet it thought you should focus your energy and attention to this one. Not just you, everybody that visited today and has either [c] in their favored tags or had previous answered many C questions. Me too.
The question was re-activated today because of a small edit by a user with sufficient rep to make edits that don't get reviewed. Systemic failure: it pushed the question ahead of all other C questions and on to your front page just because of the removal of a [tag]. Removing a tag is of course not a reason for anybody to have to look at the question again.
The user that made the edit completely missed other edits that would have been appropriate. Rather obvious ones: words like "halped" cannot possibly be missed by anybody. Systemic failure: this user was robo-editing, a pattern that is trivially detectable from the rapid pace of edits but is not stopped. I see thirty pages worth of edits in the user's activity tab -- he wasn't slowed down at all. Almost any activity at SE is rate limited, but not this one for some reason.
The user that made the edit decided to burninate the [header] tag all by himself. Systemic failure: burnination was something that was done by a hyper-privileged user. Jeff Atwood used to take care of it in the olden days. It is now supposed to be done by his successors, like Shog9 and Tim Post, paid employees of SE. They are not doing that job and largely ignore burnination requests. Vigilante user actions like this are the result.
The user that made the edit re-activated a large number of questions. All utter crap, an inevitable side effect of a questioner having no clue how to tag a question properly with the equally inevitable quality problems with the question. He got my personalized front page filled with crap. I poked at it for a while and decided I had better things to do and posted no real answers today. Systematic failure: users that edit should not be able to launch a DOS attack on other users' front pages.
The question was destroyed by the system today, surely because of the attention it got. Systematic failure: the user of course has no idea why, got no feedback is very likely to get this wrong all over again.
This is how systems fail, a chain of little problems that all combine to make a Big Problem. Something that any software engineer should be aware of :) Going back to the core problems, I hope that the editor loses his privilege but nobody can do anything to ensure that happens. This question should have been deleted two months ago to stop the first card from falling down. That cannot happen until everybody at SO just ignores the need to pick an accurate close reason from a dialog filled with weasel words written by SE employees that are worn out from the complaining. Pick anything, it does not matter on crap like this.