News for hackers. Stuff that matters.
[dead]
Re:How we built scalable spatial indexing in CockroachDB by dang on Monday December 14, 2020 @04:53PM (#25423890)
"Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents."

https://news.ycombinator.com/newsguidelines.html

The provocation is understandable but it has been done to death on HN and the principle of curiosity implies mandatory retirement.

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

Re:How we built scalable spatial indexing in CockroachDB by didibus on Monday December 14, 2020 @05:24PM (#25424207)
I'd like to understand the policy to be sure I know what to avoid in the future. Is it that the choice of name in this case was already discussed? Or is discussing the choice of a product name considered inappropriate? Or is it that the discussion of the name in this case is too tengential to the announcement of spatial indexing?

Thank You

Re:How we built scalable spatial indexing in CockroachDB by orthecreedence on Monday December 14, 2020 @08:37PM (#25425997)
> Is it that the choice of name in this case was already discussed?

About 1000 times on every single submission of CRDB, going back years and years.

In any given post about CRDB, at least half the comments are about the name. I personally don't think your parent comment is particularly inflammatory, and it seems to be more curious in nature, but it's a sensitive subject because sometimes people just want to talk about the database as a database, not as a brand.

Re:How we built scalable spatial indexing in CockroachDB by dang on Monday December 14, 2020 @08:57PM (#25426138)
It's the first, as orthecreedence explained. Though threads about product names are usually pretty shallow and don't make the greatest HN discussion, we wouldn't moderate them generally. This is a special case because there have literally been hundreds if not thousands of comments about it over god knows how many years, and once things have been repeated that often they become their own circle of hell. Thus, whenever something about this database gets posted, the main concern is whether the thread will get overwhelmed yet again by bickering about the name.

I realize it's an arcane point if you never saw any of those previous flamewars, but the

Re:How we built scalable spatial indexing in CockroachDB by didibus on Monday December 14, 2020 @09:46PM (#25426402)
Ok thanks, that makes sense to me.
Re:How we built scalable spatial indexing in CockroachDB by dang on Tuesday December 15, 2020 @12:06AM (#25427209)
That's good because I had a mangled sentence in there ("choice of product" when I meant to say "product name"). Fixed now :)

Edit: oh dear, there's also a dangling at the

(which I'll leave for amusement's sake)

Re:How we built scalable spatial indexing in CockroachDB by rando_ta_95837 on Monday December 14, 2020 @05:03PM (#25424006)
What? Of course there is a reason: there's an old adage about cockroaches being the only animals that would survive a nuclear war. Obviously not true, but is does evoke the idea of resilience/reliability to anyone that recognizes the idea.
Re:How we built scalable spatial indexing in CockroachDB by didibus on Monday December 14, 2020 @05:17PM (#25424136)
Hum, interesting, that's an angle I hadn't thought of. So it's a comparison to the reliability and durability of cockroaches. To me, it immediately evoked a disdain to the idea of having cockroaches in my house. So it had a negative association in my head. I wonder how much product names can affect marketing draw, I wonder if product research goes that far.
Re:How we built scalable spatial indexing in CockroachDB by mhuffman on Monday December 14, 2020 @05:32PM (#25424271)
fyi, I am not sure why but you will get downvoted to oblivion for asking this very reasonable question.

Obviously it is a bad idea.

You as IT head: "Hi Managerial members! Can you approve my budget increase for CockroachDB?"

Them: "Um ... WTF?"

For whatever reason though, if you point out this obvious ramification of naming something meant for B2B a really stupid name, you will get attacked and downvoted.

IDK if it is just because people brought it up before, or CDB employees brigade it or what, but that is what happens.

Re:How we built scalable spatial indexing in CockroachDB by WalterGR on Monday December 14, 2020 @05:35PM (#25424295)
> For whatever reason though, if you point out this obvious ramification of naming something meant for B2B a really stupid name, you will get attacked and downvoted.

Sooo many posts about projects will have comments / arguments about the project name. It's stupid, there's another project with the same / similar name, it should have been named this...

It's boring, requires no effort, and doesn't touch the actual subject matter of the post.

> IDK if it is just because people brought it up before, or CDB employees brigade it

I don't think a conspiracy is necessary to explain this phenomenon.

Re:How we built scalable spatial indexing in CockroachDB by mhuffman on Monday December 14, 2020 @05:39PM (#25424332)
I think you will agree this is not a normal name.

I can see a bit of an issue with innocently naming your OS app the same as something else that is already established but you were unaware of. Ok. Maybe that person even is happy to get that information.

That is not the same as this.

Also, some people (not everyone) might not read every single story on HN or do in-depth research before making a comment that is perfectly reasonable .. like the OP.