##Obsolete the rule once for all
Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many.
95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.
##Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many.
95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.
Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many.
95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.
##Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many. One answer per language is not too many.
95 snippets per answer is not too long. 95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.
##Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many.
95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.
##Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many.
95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.
##Obsolete the rule once for all
There are either too many possible answers, or good answers would be too long for this format.
One answer per language is not too many.
95 snippets per answer is not too long. Note that we have less than 200 answers with more than 95 votes on the whole site. The answers are not really expected to be that long.
Allowing doing anything is not too bad. Note that everyone can invent their own languages.
Making a single exception would just bring more arguments in these cases.
We may try to fix the wording. For example:
- There are too many apparently competitive answers.
- There are general answers irrelevant to the question.
- The answers are supposed to be big projects that practically have to consider the quality measures not objectively defined in the question.
But I'm not sure if it works. In fact, we are not a QA site and many of the rules don't apply, and we did't seem to have consensus about what is too broad on our site in the first place. Someone should post another question about the exact terms if we really want to do that.
We have 3 problems now
- Is it a bad question?
- Do we close it?
- Do we make exceptions or change the rules?
I'd say it's not a perfect question. But we are not going to close every imperfect question.
I'm not exactly sure whether we should close it or not. But we don't have to make rules to cover every case. There are cases where we should absolutely close the question, and cases where we should absolutely not, but there are also cases that it might be better to leave for the community to decide. That is, they could be technically allowed but subjectively a bit broad. If we try to make it exactly clear, it's likely our rules will be filled with contrived situations and not the obvious cases nobody is bothered to argue with.
A general rule makes sense only if it also makes some differences to other questions. But we have no idea what a question similar to this one (but isn't a duplicate) would be like. If we try to decide whether we should make exceptions, the implication is, other questions (that we had no idea what they are) similar to this one are all on-topic / all off-topic. That's indeed something ain't broken.
One reason to lock the question is to not encourage similar questions. We don't even have an idea whether we should encourage them.