Hacker News Reader

Other than "can I use <new API>" style questions, the vast majority of 2009 HTML/JS answers are still entirely valid.

Again, though, you're missing the point. On StackOverflow, a stale answer can be fixed, by virtually anyone. On traditional vBulletin-style forums, the post saying "this isn't true anymore, there's a better way" might be buried hundreds of posts in.

I agree with you to an extent, and this is especially true for iOS stuff where there's a lot of API/platform churn, and sometimes the same issue or bug pops up twice with a few years between.

I often land on a question that I'm asking, and it has a lot of upvotes, but it was answered 3 years ago using deprecated APIs.

If the API has really changed that much you can ask another similar question mentioning that you're interested in the new stuff, not the old one from the previous question.

I love old questions and answers, because if I have to rebuild something that was built in 2009, I want to see what people were saying in 2009.