I've seen plenty of "20xx: Now we do Y instead of X" answers posted years after the original answer.
> No, there is no such feature, so I made a custom hotkey: Ctrl + `
And then a few years later Microsoft implemented the feature and made the default hotkey Ctrl + `
---
I felt a bit of trepidation editing a top answer with >1k votes, but I did it: https://stackoverflow.com/posts/43012779/revisions
Probably they need a deprecate-answer feature instead.
I have answered many old questions and never once has this been flagged; usually it gets upvoted.
I have 10 "necromancer" badges: "Answer a question more than 60 days later with score of 5 or more" – some of these answered questions that were over ten years old. And this excludes the answers which haven't gathered 5 upvotes (yet).
Answering old questions is absolutely worthwhile in my experience.
The problem with this is that answers change, for some languages the way you did X 5 years ago might still be the best way to do X, but for another language it's no longer the best way of doing it. And while S.O has done a good job of moderating and make sure they are that high quality source of info, they caused a second order effect in that no one wants to post there anymore. After a while you're left with a bunch of outdated answers and no one wants to post updated answers because "it's just going to get flagged".
The authors example of any new JS answers being marked as dups and old jquery answers being provided instead is exactly what I am talking about. I hardly ever use S.O for JS questions anymore because everything is from 5+ years ago with examples in Jquery or ES5 that you have to translate to modern JS. Yeah those are high quality answers, if we were all still using Jquery.
S.O could have gone about producing the "searchable corpus of answers" in a different way that would have preserved the quality but not dejected all of it's users.