Do you really think saying you are a specialist, yet won't read about the topic you specialize in because you are scared of a benign name is reasonable?
I forgot to mention the ridiculous hyperbole comparing 'cockroach' to racial slurs.
But as others have pointed out, the name creates unnecessary conflict and discomfort. In a world of perfectly rational humans, it wouldn't matter. In the real world, it makes it harder to get stakeholders on board. That's why I made the comparison to ethnic slurs. "F_U_DB" might be the greatest storage system imaginable. It doesn't change the fact that the name alone is going to create extra unpleasant work. (EDITED to fix an error)
There are no such things as "perfectly rational humans" and if there were they would be rational and would not experience discomfort because of a name because that's irrational. A rational human would see the name as clefer if anything since cockroaches are quite enduring.
Additionally, even if you aren't personally bothered it, most would be aware that others feel this way, which certainly creates an uphill battle for the tool and diminishes the prospect of a vibrant ecosystem building up around it.
This is a red flag for anyone who might be considering including CockroachDB as an important part of their stack on any long-running project
Do you discard such factors?