It would be bikeshedding if we were all, for no good reason and without prompting, suggesting names that we preferred, with no consensus emerging. Instead what

It would be bikeshedding if we were all, for no good reason and without prompting, suggesting names that we preferred, with no consensus emerging. Instead what I see in this thread is a clear consensus that the current name is atrocious, even to the point of being detrimental to the long-term success of the project, and should therefore be changed. Personally, I refuse to use or recommend this product as long as its current name remains. And to those who think I'm being petty, 1) I can afford to be petty given how many database options (NoSQL or otherwise) are out there, and 2) market forces should punish products with names like this, or else we'll eventually find ourselves debating the merits of HerpesDB vs. ManureDB.