Remix clone Hacker News

The speaker’s claim that it’s hard to find a two-character name that hasn’t already been used for a CPU architecture seems ridiculous on its face. And his tone seems to indicate that he knows that (to me, anyway).

I programmed the real F8 back in the day, so I’m quite defensive about it. It’s most charming quirk: doing a long jump clobbers the accumulator.

▲

kjs3 2 days ago | parent [-]

[flagged]

▲

sjsdaiuasgdia 2 days ago | parent [-]

Funnily enough, I did a quick search and immediately found an E8 processor - https://www.andestech.com/en/products-solutions/andescore-pr...

Wasn't quite as strong a match for "G8", but G[n] does show up in a lot of product descriptions to indicate what generation of the product is involved.

LG also put out a phone named the G8 Thinq in 2019.

I would generally agree with the speaker that it's hard not to collide when using a 2 character name. The "for a CPU architecture" narrows the collision space substantially, which does affect the full accuracy of the statement. But the spirit of "2 char IDs are collision prone" is true.

	▲	kjs3 2 days ago \| parent [-]
		Oh, wow...never heard of the E8 or Andes, but I guess RISC-V startups are thick on the ground these days. And I can't imagine searching for G8 and not getting carpet bombed with hits for HP servers. But the fundamental question is still "why would you even want a 2 character ID in a world where searching for it (even without the massive historical name collision with F8) will make it fruitless to search for".