There are many questions asked when stack first begun becoming popular, which deal with somewhat "fundamental" features of a popular language, library or development environment.
The problem with any popular X, however, is that they tend to change.
While 10 year old questions about Fortran may still hold up quite well to scrutiny, questions about languages like C++ or environments like browsers, do not.
I'm sure many of you have ran upon many such example.
For the sake of discussion, here's one I stumbled upon recently.
How to center absolutely positioned element in div?
This is quite a "relevant" question. Centering an absolute positioned div is a task many of use could come up against at one point if we are doing web development. It's also relevant due to the implications it would bare for anyone new to CSS, as they might take away from this how absolute element's behave.
The problem here being that it was answered 8 and a half years ago, when a critical property (
transform) was either not part of CSS or not widely spread through browsers.
Meaning the top 2 answers are essentially wrong. Well, not quite wrong, but worse, misleading. They give "broken" solutions which would hurt potential viewer's understanding of CSS, besides provide an ugly solution.
This is quite an issue, because the question has 1M views.
Obviously it's a reader's responsibility to be wise about these things. But, not being able to rely upon top answers to provide a correct solution is a huge drawback when using stack. Especially when we are dealing with the kind of questions someone that's been programming for 1 week might ask. It both makes the experience more annoying and promotes bad behavior among new developers.
In light of this, should there be some way to "necro" popular threads and re-open them for a team of moderators to pick the correct answer every few years ?
"Team of moderators" here could mean anything, an easy solution would be people with some reputation in the area of the question and validation from the community.
However, the way this should be done is not what I want to get stuck on here, but rather if it should be done at all.
I feel like this will become a bigger and bigger problem in the next few years as stack gets to be more widely used and questions get older and older.