Earlier quoted context omitted.
It's not just about discussion. It's a general stance positioning the perfect against the pretty good. Here's just one example: questions often get closed as duplicate after good answers start rolling in. Sometimes, the new answers are better than the old ones. The mods argue that the users should move their answers over to the old question. Or that they should improve the old answers. It's a lot of should, should, s…
This is by far the worst problem with Stack Overflow. The mods seem to leap at the chance to mark questions that are similar, but not identical, as duplicates.
There's one easy fix for this, and several other problems with SO: Don't close duplicate questions. Just cross-reference them.
Reasons:
- Gets rid of the "This was closed because of trigger-happy
moderators failing to distinguish between 'similar' and
'identical'" problem by making that situation impossible.
- Improves answer discovery for users: If Google gets you
to almost, but not quite, the right question,
cross-referencing gets you the rest of the way.
- Improves answer discovery for users: Maybe the best answer
today isn't the same as the best answer 5 years ago.
- Improves gamification: Rewards are the lifeblood of
a site like Stack Overflow. A way of dealing with
duplicate questions that rewards users for
cross-referencing them is infinitely more in line with
SE's basic idea than one that punishes them with
public shaming.
- Reduces opportunity for petty bureaucrats to take root.
- Represents a more thoughtful, measured way of thinking
about software engineering. Many questions really can
have more than one correct answer, or the correct answer
can depend on subtle details. Which answer gets the
green check mark may have as much to do with the situation
of the asker than the quality of the answer.