For Korean and Chinese names in particular, it's sort of the opposite: family names are lower entropy (e.g. Lee, Wang, Kim) than given names, which drastically increases the chance of family-name collision. I’m a PhD student of Chinese descent, and I share a family name with lots of academic peers in my specific subfield of research, and have even co-authored with unrelated individuals who share a family name with me. Family-name citations are really ambiguous and confusing to me, so I prefer omitting them altogether and using numeric links.
It's important to scan the references to check oneself if one agrees with the selection of references, or if the author(s) omitted important work that one knows and the authors did not know or did not want to cite due to a hidden agenda (selection bias), in which case one may email them to share additional references so that they cannot say "we never knew".
I could accept numeric citekeys if and only if the HTML rendering shows me the full entry when hovering over it with the mouse cursor (as a "tool tip"); there is absolutely no need in the 21st century to manually scroll/jump to the end without coming back when you can shop the reference inline. Hypertext is there for you to make use of it (Berners-Lee [1], 2000)!
References
[1] https://search.library.wisc.edu/catalog/999902745302121/cite ;-)
If HN had HTML I could have demonstrated the hover-over idea that I desribed, but then I respect HN's minimalism, and we all value the safety and absence of spam through not having HTML on here.
Edit: example https://mirror.apps.cam.ac.uk/pub/tex-archive/macros/latex/c...
<https://gwern.net/scaling-hypothesis> (Scroll down to "Meta-Learning" where the notes start coming fast and furious.)
edit: Tooltips supplement the traditional reference section. They are not to be printed.
<https://developer.mozilla.org/en-US/docs/Web/CSS/@media>
Depending on the accuracy of the client, this could well give differing behaviours for desktop, mobile, and print output. HTML is flexible, very few designers seem willing to embrace this.
(a) [Name 2005] is much easier to mentally track if it appears repeatedly in longer text than [5] (at least for me). [5] is just [5]. [Name 2005] is "that paper by Name from twenty years ago".
(b) By using [Name 2005], I might not know which exact paper this is, but I get how recent it is w.r.t. what I am reading. In many cases, this is useful context. Saying "[5] proves X" could mean that this is a new result, or a well known fact. Saying "[Name 1967] proves X" clearly indicates that this is something that has been known for some time.
This is silly. 99% of the time, if you cite Autor et al. (2013), it'll be that Autor et al. (2013). The other 1%, it'll be another David Autor paper. The case when you guess something wrong, and really it's a different author, who then gets hurt, probably happens once a year. Meanwhile, Autor et al. (2013) immediately lets me understand what you're referencing, which [57] does not.
Personally I hate autoincrementing numeric bibkeys for the same reason I hate them everywhere -- if you remove, reorder, or combine citations, it's a huge pita to work around.
I get if you're working in latex or something you can have the bibkeys programmatically generated, but still.
So long as the bibkey is unique and has an associated value, ill always prefer something semantically meaningful in the text.
I mean, when I see a citation, I'll read the citations regardless (if it's for work etc, casually at home I'll only read it if it seems interesting or if I'm dubious). The only way I could see it being an issue is if I've already seen the citations before and somehow I'm misremembering it or ignoring some context/nuance and I decide to be lazy and not refresh the cache, but at that point it's definitely a me problem and I don't think going to the citations and looking at the source title or excerpt there will be any better.
Semantically meaningful citekeys give me useful information where I need it (in the text), as opposed to somewhere 20 pages away.
Semantically tagged so folks could style them as they wanted.
You could of course submit that as a request to the mods / dev team at hn@ycombinstor.com.
________________________________
Notes:
1. See: <https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...>