Taking the Microsoft development world as an example, over the past three years we've seen three new versions of ASP.NET MVC and a whole new .NET Framework (and ASP.NET). In jQuery world we see the same thing where we've had quite a few releases over the past three years.
One of the things I've been concerning myself about is when users vote to close new posts as duplicates of questions when older tooling and frameworks were in their prime.
With new tools and frameworks come new, improved and superior ways to solve a problem. These older questions and their answers, whilst still valid, are perhaps outmoded and we're guiding less experienced users to carry on using these older practices through close-as-duplicate.
I'm wondering if the community should be (or are) a bit more mindful when voting to close questions as a duplicates of 2-3 year old posts and ask themselves "does the older post, asked about Framework 2.0 really provide a satisfactory solution for today's Framework 5.0"?
Do we really want to be referring OP's to these older solutions such that they're code is stuck in a timewarp?