8
\$\begingroup\$

I'm questioning the usefulness of the tag. There are only 20 questions at the moment and they don't appear to have much in common. Seems like some kind of catch all tag to me. Should we burn it?

\$\endgroup\$
  • 6
    \$\begingroup\$ In most cases the tag for a specific framework should be used instead of this tag. this indicates that it is intended to be used when using frameworks, not when writing them (like library). Does indeed seem to be a "catch all" tag. \$\endgroup\$ – Simon Forsberg Sep 8 '15 at 23:54
  • 2
    \$\begingroup\$ For what it's worth, there is a difference between a framework and a library. \$\endgroup\$ – nhgrif Sep 8 '15 at 23:58
  • 1
    \$\begingroup\$ One person did use it to tag a framework they were writing, is it worth keeping on that one question? \$\endgroup\$ – SuperBiasedMan Sep 9 '15 at 10:58
  • \$\begingroup\$ @SuperBiasedMan that's a fair point, but if it stays, we need to clarify what the tag is for and clean it up. I'm open to proposals other than burnination. If I was 100% sure it needed to go, I would have just removed it. I'm not. Hence the meta. \$\endgroup\$ – RubberDuck Sep 9 '15 at 11:01
  • 1
    \$\begingroup\$ @RubberDuck I edited the tag excerpt to specify not to use it just for framework usage and use specific framework's tag in that case. \$\endgroup\$ – SuperBiasedMan Sep 9 '15 at 11:38
6
\$\begingroup\$

Burninate

From the tag wiki excerpt:

"In most cases the tag for a specific framework should be used instead of this tag."

If this tag is only supposed to be used to indicate that you're using a framework, it really doesn't serve a purpose, since we already have tags like . Let's burninate it.

\$\endgroup\$
2
\$\begingroup\$

Not every framework needs it's own tag. If a specific tag is available, use that. If not, use . It explicitly states there is no vanilla situation, which is valuable.

\$\endgroup\$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .