Putting contentious questions on probation
So at least once every day we have this kind of question where somebody asks to give advice about some technical topic. (I'm not talking about career advice, though that may be handled too). Those questions mostly get closed immediately. Often as to localized.
While I fully understand the reasons behind closing them, mainly for the knowledge base style of StackExchange, I still feel slightly bad for the users who ask those questions. From their subject those questions often fit very well to the community (best way to learn some subject, good tools to do something) and people justifiably expect that they can get good answers here. Often enough, some of the answers given before closing confirm this.
Wouldn't it be possible to add a kind of "delayed closing", that allows users to answer for maybe three days. After this period the question gets closed automatically. This way StackExchange would stay a knowledge base. Or would this still be too much "chatting"?
Maybe somebody has a better idea how this can be handled. I just think it would be nice if we at least have a chance to help some people, as long as there are users ready to answer this kind of question.
I'm not sure, if every single one would fit for such a solution, so please don't start discussions about the questions as such. Just to give some idea:
Maybe the worst example, since the questions isn't very good. But this could be enhanced instead of closing it. After all he is mainly asking for some input on C++ and how difficult people with experience think it is.
Seems to be a 'historical' question. Obviously with some interesting results.
Obviously closed for good reasons. Too localized, only interesting to one person. But within a day or two, most likely somebody would have given him a few interesting links and he would be happy. Question than auto closed and never to be seen again.
That one I really like as an example. It's too unspecified and can't be answered clearly, but is a interesting question anyway.
Difficulty here of course, that it's a duplicate of an older question. But maybe that makes it even more interesting by drawing temporary attention to te older one and allowing new users to consider adding new material.
Another one of the 'give him some interesting links and he is happy' type. Everybody interested could follow it for a few days, get some interesting information exchange and then forget it ever was asked (and in six months there would be new information anyway)
Typical 'technology-advice' question. We have the people here who use those technologies since years and can tell him everything he needs to know. Sure, no clear answer and in a few months the game may have changed toward another technology.
I can say that many answers to those questions where interesting to me. I either learned something from experienced people or maybe got a link to some interesting blog. I wouldn't know any other site were I could reliably get serious answers to such questions. So having them around for some days as a kind of 'slowed down chat' wouldn't hurt and increase the flow of information between members.
Another one that just came in and will most likely be closed soon: What's better right now: IronRuby or IronPython?
Too bad, user used a 'bad' word: better. Question is auto doomed...
Let me give an example from real life:
A few years ago I had to make a decision about how to implement full text search on a website I was writing in Ruby. There were several engines available, all of them had some community. Namely there was Ferret, which was used by many people and Sphinx which was relatively new and didn't have many users yet. But everybody who had worked with them would have told you clear enough, that Ferret had several very annoying bugs while Sphinx worked very good. There was not much discussion about this. Though the answer would have been too localized in time, since of course Ferret could have been improved. If I would ask this question here, it would be closed within minutes, just because I ask to compare two technologies based on practical experience in real world projects.