Perhaps to a large fraction of relevant stakeholders, the name is a signal of project immaturity and perhaps poor judgement. Additionally, even if you aren't p

Perhaps to a large fraction of relevant stakeholders, the name is a signal of project immaturity and perhaps poor judgement. 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?