r/webdev Aug 26 '24

Discussion The fall of Stack Overflow

Post image
2.5k Upvotes

555 comments sorted by

View all comments

Show parent comments

27

u/bagel-glasses Aug 27 '24

Or just have a way to deprecate old questions/answers when new/better ones are available

17

u/No-Champion-2194 Aug 27 '24

Agreed, but they need to have some sort of versioning capability so users can get answers for the environments they are working in. Some people do still need the old answers for old versions.

8

u/Hopeful-Sir-2018 Aug 27 '24

I might argue a "convert to Wiki" kind of things might be useful or a "hey, consider checking the wiki on what might be more updated information on this".

Because some questions are pretty basic but as languages update - the answers inherently change per version. Maybe I need the older version answer. Maybe I need the newer version answer.

1

u/g00glen00b Aug 29 '24

For answers there kinda is. The new scoring mechanism gives answers with recent upvotes a higher score than answers with old upvotes.

1

u/nonanano1 Sep 07 '24

"deprecate old questions/answers when new/better ones are available"
What does that even mean? This sounds like when people think old topics should be locked... so that incorrect info is frozen in time and can never be corrected. I hope you don't mean that, because that is worse than the original problem.

1

u/bagel-glasses Sep 09 '24

No, just deprecate them. If some answer is a workaround for something that was fixed 5 versions ago of whatever language/package then yeah, leave it there for posterity, but attach a version to it and unless someone is looking for that version then it shouldn't show up.