I noticed that in some cases, there are answers that are not answers.
The question is asking what is the difference between two modules that have the same purpose, while the answer is reporting to consider another module. Clearly, it is not an answer because it doesn't report any difference between the modules. It could be a comment, but not an answer.
The question is asking if the submitted form is rebuilt before the user is redirected; the answer reports to use
drupal_goto() to redirect a form, which is not necessary as Drupal will call the function using
$form_state['redirect']. It is not even the answer to the question, as it doesn't say if the form is being rebuild before to redirect the user to another page.
Both the answers don't answer the question, which is how to avoid somebody is able to understand that a site is running Drupal. An answer that says that securing a site by obscuring doesn't add security should be a comment; an answer would be that it is not possible to obscure the fact a site is using Drupal, as the accepted answer does.
The question is not how to create a clone of api.drupal.org. What posted is something related to the question, but the question is quite different. Saying to somebody that is looking for alternatives to api.drupal.org to use, for example, when drupal.org is not accessible, as when happened to me once, when I was not able to connect to drupal.org without using a proxy, that he can create a clone of api.drupal.org doesn't answer the question. It could also be the user is using already Drupal 7, and in that case the suggestion to create a clone of api.drupal.org would not be useful if, as I remember, the main module used for api.drupal.org doesn't have a version for Drupal 7.
There are other answers that, to a question about the setting page of module A, or how to do something with module A, replies with "Use module B." or "Consider using module C."
Are we being too permissive on the kind of answers being posted?
Drupal answers, as any SE site, is not a forum; what posted as answer should be an answer. If what posted as answer really answers to the question, and then adds a comment such as "I suggest you not using that module." or "I suggest you not doing what you are trying to achieve." then it is fine. If then what the OP is asking it is not possible to achieve, then the answer should report that is not possible to do what the OP is asking, and then adding it is not suggested to try to achieve what described in the question; in that case, the answer could report the reason why is not suggested to do what the OP is trying to do. As alternative, the part suggesting not to do what the OP wants to do could be placed in a comment.