[quickthrower2]

Not their fault but old answers really suck. A 2016 answer about Azure is useless. Even a 2016 answer about react.

Also it’s a trope that the select answer isn’t always the best so there is a meta conversation about what is the “really best” answer

[egfx]

I disagree that old answers are useless.

Frontend JavaScript frameworks are actually a good example. If you wanted to use ENYOjs, an amazing but seemingly defunct framework. You couldn’t go to the website because the whole thing was turned into a react fork and the original documentation was deleted. Besides stackoverflow you’re stuck and what if you have to maintain an old enyo project on roku or another web based platform? What if you are basing your project on some open source work from the past? Anyway there are many cases where old answers are useful and sometimes more useful then new answers.

I do agree it’s extremely helpful when answers are continually updated with the times. But that doesn’t always happen but it’s nice.

[Udik]

I agree, and it unnerves me because the solutions seem to be easy. Just allow users to tag an answer as outdated, or to add a "valid until YYYY" tag. This would provide a quick indication when skimming answers, without removing old ones. It could also allow to reopen an old question in case the accepted answer or all its answers are marked as outdated.

[milkey_mouse]

> Just allow users to tag an answer as outdated

StackOverflow is testing such a feature right now: https://meta.stackoverflow.com/questions/407613/outdated-acc...