IMO this is a stronger reason - it's not that nobody gets the intended meaning, it's that enough people get the unintended one and every HN thread is derailed.

IMO this is a stronger reason - it's not that nobody gets the intended meaning, it's that enough people get the unintended one and every HN thread is derailed. If that's the sentiment on a community with downvotes and a strong culture of "we just care about the technical issues", imagine the sentiment on a team considering adopting it. FWIW I will never proactively advocate for this DB or try it out because I don't want other coworkers to feel squicked. I'll do my job if I find myself on a team using it, of course, but in my many years working on software, I've found that you can't make the computers happy unless the people typing into the computers are happy. Limiting the pool of people who can be happy reading CockroachDB docs when they're paged at 2am for an outage seems not worth the chance that it might page us at 2am slightly less.