For those that don't know, a brief history lesson... There are two distinct variants* of Visual Basic:
- The old COM-based platform, which was last released under the name VB 6 back in 1998.
- The newer .NET-based platform, originally called VB.NET, but now just called "VB" by Microsoft since VB 6 has been dead for so long.
Unfortunately, this naming/identity crisis means that the vb tag conveys little to no useful information, and our usual weapons (synonyms) are useless here. It's not clear whether someone using this tag actually means vb6 or vb.net. And if it can't be deduced from the sample code or the other tags, we have to ask them in the comments and then retag the question. Every time. That workflow is broken.
Worse, users like Joel Coehoorn periodically go through the questions with the vb tag and try to rectify this ambiguity. That's all fine and good, but it "bumps" a large number of old questions when there is not actually any [meaningful] new activity. Since I frequently look in this list for questions to answer and the VB-related tags are included in my favorites, this is a continual source of noise for me to wade through.
Thus, I propose that the tag shouldn't even be available for use on new questions. Having it available just encourages people to use it when they really shouldn't, and that just creates extra work for other dedicated users. Yes, we could put this information in the tag wiki summary for the vb tag, instructing people to use one of the other tags, but we all know no one actually reads that stuff.
The only counter-argument I can envision is "an ambiguous tag is better than no tag", but that problem solves itself. The question submission system won't let you post a question without any tags, and if you really can't figure out which one to use, well then we probably don't want your questions anyway.
* Nitpicker's Corner: There might actually be more than two variants of Visual Basic when you consider VBScript and Visual Basic for Applications (VBA), but these are syntactically and otherwise quite similar to VB 6, so I don't think they merit their own categories here.