This was a particularly crappy question a few days back. Now there is not even a trace of it. This question did not get any answers, but got at least 3 (meaningful) comments. But I've seen a few question in this general theme, at least once every few days. The general theme of this type of question is (which I call coding by crowd sourcing):
- Try writing some code or try some example from some site, and when something goes wrong
- Don't try to troubleshoot it, post it on Stack Overflow
- Find out you're doing something embarrassingly wrong (such as compiling the wrong file, compiling in the wrong directory, not compiling, not saving before compiling, etc), and remove the question
I think that since the system is too lenient letting posters immediately and at no cost to them remove a question, this is a self perpetuating problem. One that encourages coding by crowdsourcing and wasting of the community's time.
Can this be handled by the system better? The real question is: would it be possible to harshly penalize questions that quickly get closed (voluntarily or not), and reward volunteers that make that happen?
My suggestion is, when someone posts, open an "escrow" with 10 rep points (maybe more). For every 10 minutes your question survives, you get 1 rep point back from escrow. When and if it is closed all users that voted to close, and all commentators, that helped point out the crappiness of the question, split the escrow.