It's just that those goals (i.e. "we want people to be able to search for information and find high-quality answers to well-scoped, clear questions that a reasonably broad audience can be interested in, and avoid duplicating effort") don't align with those of the average person asking a question (i.e. "I want my code to work").
I have heard so many times about how people get insulted for asking questions on SO. I have never been shown it actually happening. But I have seen many examples (and been subjected to one or two myself) of crash-outs resulting from learning that the site is, by design, much more like Wikipedia than like Quora.
Quite a large fraction of questions that get closed boil down to "here's my code that doesn't work; what's wrong"? (Another large fraction doesn't even show that much effort.) The one thing that helped a lot with this was the Staging Ground, which provided a place for explicit workshopping of questions and explanation of the site's standards and purpose, without the temptation to answer. But the site staff didn't understand what they had, not at all.
This explains the graph in question: Stackoverflow's goals were misaligned to humans. Pretty ironic that AI bots goals are more aligned :-/
That is not a reason for fishing instructors to give up. And it is not a reason why the facility should hand out fish; and when the instructors go to town and hear gossip about how stingy they are, it really just isn't going to ring true to them.
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/
> "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!
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).
It is explicitly understood to be doing a favour to the OP: an already-existing answer to a common question is provided instantly.
