For me SO could be more powerful if more answers would link or refer to documentation/github landing pages supporting/documenting their solution.
Often I see some weird way to implement something in the .NET world, especially Core/.NET 5, search Microsoft docs and find an 5-10-min read article updated last Wednesday that explains in-depth (relatively to a SO post) three different newer way of doing it.
A big weakness of SO, as I see it is aging. Most upvotes and marked-as-answer is most likely also the oldest.
Maybe the page could warn for old answers or highlight newer answers that are gaining traction.
Maybe questions and answers should be encouraged to specify version of tools. Asking identical questions for V1 and V2 of a tool should not be met by "POSSIBLE DUPLICATE" warning or get downvoted to oblivion. Posts shouldn't need "EDIT 1 updated for V1", "EDIT 2 updated for V2", as this is OK with 2 versions but what about 10?
Maybe points (or some score system) should decay over time? Idk. But I think something needs to be done.
Often I see some weird way to implement something in the .NET world, especially Core/.NET 5, search Microsoft docs and find an 5-10-min read article updated last Wednesday that explains in-depth (relatively to a SO post) three different newer way of doing it.
A big weakness of SO, as I see it is aging. Most upvotes and marked-as-answer is most likely also the oldest.
Maybe the page could warn for old answers or highlight newer answers that are gaining traction.
Maybe questions and answers should be encouraged to specify version of tools. Asking identical questions for V1 and V2 of a tool should not be met by "POSSIBLE DUPLICATE" warning or get downvoted to oblivion. Posts shouldn't need "EDIT 1 updated for V1", "EDIT 2 updated for V2", as this is OK with 2 versions but what about 10?
Maybe points (or some score system) should decay over time? Idk. But I think something needs to be done.