But SE is not YouTube. On the latter, it doesn't matter what comment has the most likes. On SE however, one can say that what answer gets the most upvotes is t

But SE is not YouTube. On the latter, it doesn't matter what comment has the most likes. On SE however, one can say that what answer gets the most upvotes is the most important aspect of the site. For me, the date of the answer had become a key information to check before I even reading the answer. I use Django a lot and it significantly evolved over the years. And for too many times, I'd spend time implementing a solution, only to realize it no longer worked since version x.y that was published z years ago. The thing is, stack exchange was built to serve an industry characterized by its very rapid evolution overtime. Yet, it fails, IN MY OPINION, to adress such a key element in a graceful way. The documentation industry solved this years ago. Going back to Django again, its doc site allows users to select the version they're interested in order to show them relevant content. I think stack exchange needs to implement something similar for its answers. How can that work? Well, users can be allowed to add tags to mark versions where they know the solution doesn't apply anymore. It may not be the earliest version where this issue arises, and that's understandable. Other users can later refine the threshold data. SE can then display the info where searchers can easily spot it [Answer not applicable since x.y] and avoid them some confused head scratching. We can push this even further with multiple correct answers for a single question, depending on the version. Users can even add the version of different software they're interested in and see the correct answer that applies higher, regardless of number of upvotes. (Written on my phone. Apologies for typos.)