Just today I have probably worked with at least 20 code libraries with their own documentation, and most of those libraries will be replaced within 3 years from now.
I think reading the documentation for everything that a webdev works with now could be a full time job in itself.
It's unbelievably annoying when this happens. I have a number of bookmarks to incredibly insightful posts, whose usefulness has been corroborated by literally hundreds of people...all closed because they are deemed "off-topic" or some such by an admin.
My theory is that SO was essentially "done" years ago. But people are still on staff and needed something to do. Thus, unrelenting navel gazing ensued.
Imagine the question : "What is the best templating engine to use for Django?" This question doesn't have an answer, because it's so dependent on use case (even that statement is controversial). So if it's on SO and not closed, you'll get a bunch of answers that are contradictory, and people flaming in the comments.
I think the main objective for the SO team is to have people land on the site and _have their answer right there_. By removing possibilities of these off-topic questions, you're less likely to land on answers that help your specific thing.
End result is "when I land on SO I get an answer every time" instead of "when I land on SO sometimes I get a flame war". For branding, at least, I think it works in their favor to close those questions
e.g. http://stackoverflow.com/questions/257712/best-web-applicati...
or less seriously:
http://stackoverflow.com/questions/184618/what-is-the-best-c...
Also, smart, general questions are not the only questions to be closed: I got one closed on networking because the problem was between two company networks, not inside. There is an obvious reason for a rule about company networks and that is to keep hone networking out, not because we need another subsection for WANs, no?
This is wrong in multiple dimensions and [edit: the next sentence which i didn't quote is] flamebait.
One camp believes in following these guidelines to a fault. The other camp thinks some of the rules are counterproductive to SO's principles.
Source: http://stackoverflow.com/help, the guidelines are clearly outlined.
I don't understand why I have to click another link to go to another site that doesn't have the same context and awareness of where I just came from.
For example, where is the guideline that answers this without ambiguity?
http://meta.stackoverflow.com/questions/261592/how-much-rese...
I've some sympathy for that.
What do you think happens when the two are rewarded equally, but the latter can be done much more frequently per unit of time?
Heck, even if the site was only for "novel" questions, according to your logic, only the most important unanswered question should be visible, until it is answered. Otherwise people might be incentivized to answer the second most important question instead.
I don't think they're mutually exclusive - there are multiple reward structures for multiple types of players. Both should be encouraged.
Further, there's the question of how much effort the questioner should be expected to put in. In a great many technical question fora, the experience is that many noobs make no attempt to search out answers.
So, yes. Internet points.
I'm not suggesting we leave obviously terrible questions open, it's the borderline posts that get me. Interesting questions which may not have a black and white answer, but would still encourage discussion/opinions which would be useful to people down the road. I know "it's not a discussion site", but sometimes there are gray areas and it's useful to have the opinions of experts on the pros and cons of certain approaches/technologies/whatever.
I suspect that SOs answer to your need is "Go use a different site". At some point, that becomes a reasonable answer.
The problem is that you can't boil down development to very focussed questions with very focussed answers.
A lot of answers are experience and opinion - and if someone experienced is giving an opinion that's usually useful in itself, dammit, even if someone else with experience disagrees.
'Is React better than Angular?' may seem pointlessly open, but if you get answers from two camps who both know what they're talking about, it's possible to learn a lot from both.
In my experience, this is completely false, it should be reworded as "Questions that moderators like to remove on a whim".
The fact that a moderator (or group of moderators) don't find a question valuable doesn't mean that it is not valuable for the rest of the world, and this applies specifically with questions about recommendations.
I have gotten a _lot_ of value from closed SO questions that were high ranked in my Google search results.
I don't know what that says about SO's flagging system, but it is what it is, I guess.
Too bad for you, it just takes an overzealous moderator to remove a closed question that many people find valuable.
Your best bet is to bookmark the question and trigger archive.org's crawler via the "Save Page Now" form: https://archive.org/web/
Also in the rapidly changing JS world they don't reference the version consistently. Code that worked fine on version 1 doesn't work six months later on version 1.1, if I knew the version it would save a lot of time.
What I would think would be better is for questions that receive a lot of upvotes after they are closed, that the people who flagged the question have reduced capability to flag down questions in the future.
how to push an item into an array in Java?
The obvious response is "lol don't you know how to read the doc"?
Yet the view count is over 100,000 and counting, with people commenting how much they appreciate finding the answer immediately.
So that's an example of a good question, actually. And an answer "read the docs" would be down-voted as unhelpful and quickly disappear.
Roughly, there are two camps. Those who say that any well-formed, non-dup question of interest should be let in and those who think it's a stop of last-resort after checking all conceivable documentation and scouring the internet.
I believe the latter viewpoint is pretty run-of-the-mill developer machismo, and it makes me chuckle every time the first google hit directs me to a SO post with 1000 upvotes that has been closed as "off-topic".
It seems self-evident to me that in the year 2015, the internet has allowed me to make more valuable use of my time quickly searching for answers rather than scouring documentation. Docs have a time and a place, but are not needed for quick dips into the myriad techs you need to use to write a typical app these days.