This question already has an answer here:

I feel that the brand tags such as and can be misused and create too broad of questions.

Should we remove these or put more stern wiki text for them?

As LBT has noted, this has been brought up before? Can we make an effort to remove these for good?

marked as duplicate by Daniel A. White, Won't, hims056, Tobias Kienzler, Martijn Pieters Oct 1 '13 at 14:51

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Should we remove the stackexchange tag from Meta too? – Oded Oct 1 '13 at 13:32
  • @Oded i think if its used as a "general" purpose tag, then yes. – Daniel A. White Oct 1 '13 at 13:33
  • 1
    @Oded I would say yes, since almost all questions (anything not specific to stack overflow, which is most questions) should have it, and yet don't – Richard Tingle Oct 1 '13 at 13:35
  • 5
    Sigh. Tongue firmly and decisively removed from cheek by the Community. – Oded Oct 1 '13 at 13:41
  • 1
    Related: meta.stackexchange.com/questions/190914/…. FWIW, I spent a couple minutes a day removing the [Microsoft] tag from questions, but got bored after a few weeks of not getting anywhere. – LittleBobbyTables Oct 1 '13 at 13:43
  • C compilers can be distributed by many companies, so adding compiler's brand to the question, for example, seems legitimate to me. But that's just my two cents here, I'm not regular on SO so what do I know? ;) – Mołot Oct 1 '13 at 13:44
  • 1
    @Mołot most of those compilers have names like borland-c, gcc or visual-c. – Daniel A. White Oct 1 '13 at 13:45
  • @DanielA.White consider adding this aspect directly to your question, then :) – Mołot Oct 1 '13 at 13:47
  • @Mołot For a tag to be appropriate there would need to be questions for which the tag could be the only tag on the question. That would never be the case in such an example. It's a case where the information can be included in the question and doesn't need to be specifically in a tag. – Servy Oct 1 '13 at 13:52