[foobarbecue]

Would you mind linking me to an example or two? I've seen this type of complaint often on HN, but never really observed that behavior on SO, despite being active on there for 15 years. I guess maybe I was part of the problem...?

[threecoins]

Here is one fine example. [1]

The person taking offense was member of C# language design team mind you. There are several such cases. This was particular question I stumbled upon because I wondered the same question and wanted to know what were the reasons. This was perfect Lucky Ten Thousand [2] moment for him if he wanted.

[1] https://stackoverflow.com/questions/59193144/why-is-c8s-swit... [2] https://xkcd.com/1053/

[rob802]

You're right - those comments are unacceptable. Honestly, it's out of character for that person. I've deleted them but will preserve them here:

> "Why not?" questions are vague and hard to answer satisfactorily. The unsatisfactory answer is: did you personally do the work to add this feature to the language? The language is open-source, you want the feature, so why have you not done it yet? Seriously, why not? You've asked a why not question, and you should be able to answer it yourself. Now ask every other person in the world why they did not add the feature either, and then you will know why the feature was not added. Features do not appear magically and then need a reason to remove them!

> Moreover, you say that the feature is simple and fits well, so it should be straightforward and simple for you do to the work, right? Send the team a PR!

[js8]

I think PP means it's more in the tone and passive-aggressive behavior ("closed as duplicate") than somebody explicitly articulating that.

It's a paradox of poor communication that you cannot prove with certainty that there is an intent behind it. There is always the argument that the receiver should have known better (and bother checking local news at Alpha Centauri).

[zahlman]

There is nothing "passive-aggressive" about closing a question as a duplicate.

It is explicitly understood to be doing a favour to the OP: an already-existing answer to a common question is provided instantly.

[CamperBob2]

The person best qualified to assess the relevance of any previous answers is often the OP. Far too often, the already-existing answer is years old and either no longer the best answer, or doesn't actually address a major part of the question. Or it simply was never a very good answer to begin with.

What would be the harm in pointing out previous answers but leaving the question open to further contributions? If the previous answer really is adequate, it won't attract further responses. If it's not, well, now its shortcomings can be addressed.

Closing duplicates makes as much sense as aggressive deletionism on Wikipedia. It generally means that somebody missed their true calling on an HOA board somewhere.

[zahlman]

> The person best qualified to assess the relevance of any previous answers is often the OP.

The purpose of having the answer there is not to solve the OP's problem. It is to have a question answered that contributes to the canon of work. This way, everyone can benefit from it.

> What would be the harm in pointing out previous answers but leaving the question open to further contributions?

Scattering the answers to functionally the same question across the site. This harms everyone else who wants an answer to that question, and is then subject to luck of the draw as to whether they find the actual consensus high-quality answer.

You might as well ask: what would be the harm in putting a comment in your code mentioning the existence of a function that serves your purpose, but then rewriting the code in-line instead of trying to figure out what the parameters should be for the function call?

> Closing duplicates makes as much sense as aggressive deletionism on Wikipedia.

This analogy makes no sense. The Wikipedia analogue is making page synonyms or redirects or merges, and those are generally useful. "Deletionism" is mainly about what meets the standard for notability.

[CamperBob2]

Scattering the answers to functionally the same question across the site. This harms everyone else who wants an answer to that question, and is then subject to luck of the draw as to whether they find the actual consensus high-quality answer.

So instead, it's considered preferable that the best possible answer never be allowed to emerge, unless by sheer coincidence the best answer just happened to be the one that was accepted the first time the question was asked, several years ago.

There's really no need for us to rehash SO rules/policy debates that have raged since day one. The verdict seems to have more-or-less delivered itself.

[zahlman]

> So instead, it's considered preferable that the best possible answer never be allowed to emerge, unless by sheer coincidence the best answer just happened to be the one that was accepted the first time the question was asked, several years ago.

What? No. The canonical target isn't closed. So go write the new answer there. The answer acceptance mark is basically irrelevant, and the feature ill-conceived.

Except usually there are dozens of answers already; the best possible answer has emerged; and people keep writing redundant nonsense for the street cred of having an answer on a popular Stack Overflow question.

> The verdict seems to have more-or-less delivered itself.

We do not care that people don't want to come and ask new questions. There are already way, way too many questions for the site's purpose. The policy is aimed at something that you don't care about. The result is a "verdict" we don't care about.

[foobarbecue]

I will say that I had questions erroneously closed as duplicates several times, but I always understood this as an honest mistake. I can see how the asker could find that frustrating and might feel attacked... but that's just normal friction of human interaction.