We can't have CVE-1234, no no, must be RageBoner or PantShitter or no one will take it seriously!
We can't have CVE-1234 exactly because no one will take it seriously, though I suspect you have the cause and effect reversed.
When the CVE list numbers in the tens of thousands and contains everything from the trivial (program may crash) to the severe (remote code execution), CVE numbers are meaningless. It doesn't tell me just how important this vulnerability is and whether I should be concerned. Whereas if someone takes the time to name it, it means it was important enough to get a real name.
Which is a terrible precedent to set, but if anyone has a better suggestion for naming vulnerabilities that gives them unique, easily communicated names, and in the process makes it clear whether they're a significant threat or not, well then I'm all ears. Otherwise for the time being, this is like complaining that people call oranges oranges rather than Citrus x sinensis.