There are already policies in place for questions that are too broad: edit them to limit their scope or close them. That's what the not a real question close reason is for.
Community Wiki is a tool for allowing the community to take ownership of a question or answer, it's to say "Hey, I got the ball rolling, can you help me fill out the rest?", it's not a tool to be used to allow borderline-to-bad questions to exist.
As to the question you're using as an example of something that you feel is just as broad as the one that got a single close vote, it was asked before the Great Redisiplining Great Redisiplining and hasn't had much activity since. Two wrongs don't make a right: just because a similar question stayed open doesn't mean a bad question gets a free pass. However, it's good to point out questions that slip through the cracks so others can take the appropriate action, like closing, on them.
But I emphasize single close vote because you're taking one single, solitary close vote far too personally. It takes 5 regular users with 3,000+ rep or a moderator to close a question. The moderation of this site is done by real people who make real choices and real interpretations of what the policies are. Many times people agree, perhaps just as often they don't. That's why it takes 5 people to close.
But the question, as it stands now, looks to be fine, although borderline with the quality of the answers it's getting.
And honestly, Programmers.SE is in no dire straits when it comes to people asking questions. There are tons of questions being asked, beyond the two you're focusing on, that aren't too broad; we don't need to make a special exception for overly broad questions.
There are already policies in place for questions that are too broad: edit them to limit their scope or close them. That's what the not a real question close reason is for.
Community Wiki is a tool for allowing the community to take ownership of a question or answer, it's to say "Hey, I got the ball rolling, can you help me fill out the rest?", it's not a tool to be used to allow borderline-to-bad questions to exist.
As to the question you're using as an example of something that you feel is just as broad as the one that got a single close vote, it was asked before the Great Redisiplining and hasn't had much activity since. Two wrongs don't make a right: just because a similar question stayed open doesn't mean a bad question gets a free pass. However, it's good to point out questions that slip through the cracks so others can take the appropriate action, like closing, on them.
But I emphasize single close vote because you're taking one single, solitary close vote far too personally. It takes 5 regular users with 3,000+ rep or a moderator to close a question. The moderation of this site is done by real people who make real choices and real interpretations of what the policies are. Many times people agree, perhaps just as often they don't. That's why it takes 5 people to close.
But the question, as it stands now, looks to be fine, although borderline with the quality of the answers it's getting.
And honestly, Programmers.SE is in no dire straits when it comes to people asking questions. There are tons of questions being asked, beyond the two you're focusing on, that aren't too broad; we don't need to make a special exception for overly broad questions.
There are already policies in place for questions that are too broad: edit them to limit their scope or close them. That's what the not a real question close reason is for.
Community Wiki is a tool for allowing the community to take ownership of a question or answer, it's to say "Hey, I got the ball rolling, can you help me fill out the rest?", it's not a tool to be used to allow borderline-to-bad questions to exist.
As to the question you're using as an example of something that you feel is just as broad as the one that got a single close vote, it was asked before the Great Redisiplining and hasn't had much activity since. Two wrongs don't make a right: just because a similar question stayed open doesn't mean a bad question gets a free pass. However, it's good to point out questions that slip through the cracks so others can take the appropriate action, like closing, on them.
But I emphasize single close vote because you're taking one single, solitary close vote far too personally. It takes 5 regular users with 3,000+ rep or a moderator to close a question. The moderation of this site is done by real people who make real choices and real interpretations of what the policies are. Many times people agree, perhaps just as often they don't. That's why it takes 5 people to close.
But the question, as it stands now, looks to be fine, although borderline with the quality of the answers it's getting.
And honestly, Programmers.SE is in no dire straits when it comes to people asking questions. There are tons of questions being asked, beyond the two you're focusing on, that aren't too broad; we don't need to make a special exception for overly broad questions.
There are already policies in place for questions that are too broad: edit them to limit their scope or close them. That's what the not a real question close reason is for.
Community Wiki is a tool for allowing the community to take ownership of a question or answer, it's to say "Hey, I got the ball rolling, can you help me fill out the rest?", it's not a tool to be used to allow borderline-to-bad questions to exist.
As to the question you're using as an example of something that you feel is just as broad as the one that got a single close vote, it was asked before the Great Redisiplining and hasn't had much activity since. Two wrongs don't make a right: just because a similar question stayed open doesn't mean a bad question gets a free pass. However, it's good to point out questions that slip through the cracks so others can take the appropriate action, like closing, on them.
But I emphasize single close vote because you're taking one single, solitary close vote far too personally. It takes 5 regular users with 3,000+ rep or a moderator to close a question. The moderation of this site is done by real people who make real choices and real interpretations of what the policies are. Many times people agree, perhaps just as often they don't. That's why it takes 5 people to close.
But the question, as it stands now, looks to be fine, although borderline with the quality of the answers it's getting.
And honestly, Programmers.SE is in no dire straits when it comes to people asking questions. There are tons of questions being asked, beyond the two you're focusing on, that aren't too broad; we don't need to make a special exception for overly broad questions.
There are already policies in place for questions that are too broad: edit them to limit their scope or close them. That's what the not a real question close reason is for.
Community Wiki is a tool for allowing the community to take ownership of a question or answer, it's to say "Hey, I got the ball rolling, can you help me fill out the rest?", it's not a tool to be used to allow borderline-to-bad questions to exist.
As to the question you're using as an example of something that you feel is just as broad as the one that got a single close vote, it was asked before the Great Redisiplining and hasn't had much activity since. Two wrongs don't make a right: it's good to point out questions that slip through the cracks so others can take the appropriate action, like closing, on them.
I emphasize single close vote because you're taking one single, solitary close vote far too personally. It takes 5 regular users with 3,000+ rep or a moderator to close a question. The moderation of this site is done by real people who make real choices and real interpretations of what the policies are. Many times people agree, perhaps just as often they don't. That's why it takes 5 people to close.
But the question, as it stands now, looks to be fine, although borderline with the quality of the answers it's getting.
And honestly, Programmers.SE is in no dire straits when it comes to people asking questions. There are tons of questions being asked, beyond the two you're focusing on, that aren't too broad; we don't need to make a special exception for overly broad questions.
There are already policies in place for questions that are too broad: edit them to limit their scope or close them. That's what the not a real question close reason is for.
Community Wiki is a tool for allowing the community to take ownership of a question or answer, it's to say "Hey, I got the ball rolling, can you help me fill out the rest?", it's not a tool to be used to allow borderline-to-bad questions to exist.
As to the question you're using as an example of something that you feel is just as broad as the one that got a single close vote, it was asked before the Great Redisiplining and hasn't had much activity since. Two wrongs don't make a right: just because a similar question stayed open doesn't mean a bad question gets a free pass. However, it's good to point out questions that slip through the cracks so others can take the appropriate action, like closing, on them.
But I emphasize single close vote because you're taking one single, solitary close vote far too personally. It takes 5 regular users with 3,000+ rep or a moderator to close a question. The moderation of this site is done by real people who make real choices and real interpretations of what the policies are. Many times people agree, perhaps just as often they don't. That's why it takes 5 people to close.
But the question, as it stands now, looks to be fine, although borderline with the quality of the answers it's getting.
And honestly, Programmers.SE is in no dire straits when it comes to people asking questions. There are tons of questions being asked, beyond the two you're focusing on, that aren't too broad; we don't need to make a special exception for overly broad questions.