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.
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.
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.
[flagged]
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.
1 reply →