Our field is pretty dynamic and things are constantly in change. What the "right way" was to fix a problem in 2009 is completely wrong today. For example, a recipe to install Ruby on Mac OS X from 2008 - using ports - is probably not the best solution today. I see some answers being downvoted today, because their solutions "don't work" anymore or they aren't the best approaches nowadays. Is it fair for those to get downvoted because they're old? How can we solve it?
Maybe we could:
- Highlight the age of a question/answer
- In our FAQ write that "before downvoting, look back in time, when the question was answered and the solution was available"
- Don't allow downvotes on old questions/answers