Now, there's nothing wrong with Go (other than the fact that I don't think I'll be bothering to learn it anytime soon), but it's providing us with a nice test drive of what will happen to the StackOverflow system when a new language/tool/framework/platform/whatever is released and the site is suddenly flooded with questions about it.
There are some good questions about Go, but there are also some others that are at least a little questionable. In this particular case, the community has decided that the question is "not a real question." This is clearly incorrect - there's a question mark, and it would be a valid question for [insert your favorite language here], but it's not a valid Go question at this time, since the language has been around for 48 hours. In fact, looking at the list of reasons to vote to close, none of them match:
- Exact Duplicate - Nope, there's no other question like this for the Go language yet.
- Not Programming Related - Nope, Go is clearly a programming language.
- Subjective and Argumentative - I'm not a fan of "list some libraries/frameworks for me"-type questions, but it's certainly not subjective or argumentative. Frameworks can be discussed and compared in terms of what they offer without a question being subjective or argumentative.
- Not a Real Question - Nope, it's a question.
- Blatantly Offensive - I won't even waste my time explaining why this isn't a valid close reason for this question.
- No Longer Relevant - This might be true for a question about using Go (or anything) on punch cards, or using an outdated API from a dead library in Go, but it's not relevant here.
- Too Localized - This is the only one I could really buy, but even this doesn't quite seem right (possibly since so few questions get closed for this reason).
- Belongs on meta.stackoverflow.com / serverfault.com / superuser.com - Nope, it's obviously programming related.
- Spam - Unless the OP was trolling (as (sarcastically?) suggested in a comment), this is obviously not the case.
So it seems that we might have a valid reason to add a closed as not yet relevant reason. Do you think we might need this reason, or do you think the current set of close reasons can handle a few oddball Go (and other languages to be released in the future) questions like this? Or do you think that this is such a rare case as to not merit messing with the system?