While I agree that precision is necessary, is it really that hard to say something like a complete inner product space vs a Hilbert space? Should we have an argument about whether we should call the triangle inequality the Cauchy-Schwarz or the Kantorovich inequality? How many years did it take to recognize Karush for providing algebraic optimality conditions long before Kuhn and Tucker?
Anyway, outside of general griping about names, very specifically, I have to regularly interact with technical people in other fields and memorizing names is one additional, often superfluous, barrier to their understanding. Even if it's important for someone credit the (supposed) originator outside of a citation, giving an intuitive name for the context would go a long way in improving understanding. For example, the triangle inequality from Cauchy and Schwarz or the algebraic optimality conditions from Karush, Kuhn, and Tucker.
By the way, I'll also mention that the majority of other mathematicians that I know don't feel this way and prefer using names after people. I understand; I just disagree.
imo, "Hilbert space" is a lot easier to read, you really only have to recognize the guy's name, it's a fairly easily recognizable word. "Complete inner product space" has me look more closely at more words, and it's all extremely boring-looking words so they don't even stand out in a block of text.
The Wikipedia article for Dijkstra's algorithm gives an alternative name of "Shortest Path First", or "SPF algorithm", which I do think is a much better and more descriptive name.
It also made me think of sorting algorithms, which all have wonderfully snappy and descriptive names. I think the world would be a sadder place if – instead of quicksort, mergesort, and heapsort – we had to struggle with opaque names like Hoare sort, Neumann sort, and Williams sort.
Well, bubble, shell, insertion and merge, sure. Quick less so. And then there is Tim...
I recently learned that in Polish, "nagle" can mean "all at once" - not pronounced the same, but still a cute coincidence!
Star-autonomous category constructions?
> Girard's paradox
Provability paradox?
> Calabi-Yau manifold
Smooth n-dimensional complex manifold?
> Dijkstra's algorithm
Shortest-path-first algorithm? (I'm cheating here because this is literally an already-common alternative name for it)
> Haber–Bosch process
Ammonia synthesis loop? (Also cheating here, since the "Ammonia production" Wikipedia article uses this exact terminology)
> Otto cycle
Four-stroke cycle? (Cheating yet again, since Wikipedia states: "This is why the four-stroke principle today is commonly known as the Otto cycle and four-stroke engines using spark plugs often are called Otto engines.")
Non-Otto four-stroke cycles abound (cf. Diesel cycle); new industrial methods for ammonia synthesis come into existence every few years and there's not much point in singling one out and calling it _the_ ammonia synthesis loop. The case of shortest-path algorithms has been thoroughly discussed upthread. Your suggestion for Calabi-Yau and Girard's paradox are not coherent with the meanings of these terms.
No big deal: giving a purer meaning to the words of the tribe is not easy, and requires deep domain expertise. And those with deep domain expertise do think about this task, have some strong incentives to think about it (teaching evaluations factor into promotion and tenure) and generally do fairly well at it.
(Startup idea: your-jargon-reform-is-bad as a service, backed by GPT-3?)
The last three, like I mentioned, were pretty much direct from Wikipedia.
But yeah, I'm under no pretense that these are necessarily correct. My only point is that we can surely do better than "$person $thing" for nomenclature. The Otto cycle is a perfect example; sure, "four stroke cycle" might be too broad, but "spark-ignited four stroke cycle" (maybe abbreviated to SI4C) doesn't seem to be (there are technically other such cycles, but the vast majority of the time people talk about a spark -ignited four-stroke cycle they're talking about an Otto cycle or some evolution thereof).
Now that I have a job a similar problem appeared with translations, Microsoft has this annoying habit of translating useful technical error messages and many times the error in Spanish doesn't yield any useful information on Google searches (if at all) so I'm again having to guess-translate terms into their original form.
But I think it's important to keep Teichmuller around as a reminder of the important lesson (especially around here) that mathematical genius does mean that everything one says on all topics is logically or morally correct.
As Teichmuller wrote: > I am not concerned with making difficulties for you as a Jew, but only with protecting – above all – German students of the second semester from being taught differential and integral calculus by a teacher of a race quite foreign to them. I, like everyone else, do not doubt your ability to instruct suitable students of whatever origin in the purely abstract aspects of mathematics. But I know that many academic courses, especially the differential and integral calculus, have at the same time educative value, inducting the pupil not only to a conceptual world but also to a different frame of mind. But since the latter depends very substantially on the racial composition of the individual, it follows that a German student should not be allowed to be trained by a Jewish teacher.[8]
It'd be hard to deny that descriptive terms are easier to memorize. Sometimes a piece of natural and/or physical intuition allows such terminology to arise.
Scientist and mathematicians do tend to think about terminology quite frequently: communicating with other scientist and mathematicians is a major part of doing science, and "the reviewers couldn't follow your argument" is a valid, and not especially rare reason for rejected articles in mathematics. Given the amount of thought put into it, "intuitive" names do tend to come about when possible (as it happened with what we now call the Ham Sandwich theorem, the concept of Fibration, the Squeeze Lemma, and countless others).
Given that mathematicians do put thought into terminology, there's often a good reason for not having more intuitive names: maybe no good common-sense intuition was available (e.g. Chu constructions are too general for this sort of thing), or the thing comes up only in highly specialized contexts where it's not worth bothering with it (e.g. Girard's paradox), or there are too many different metaphors that one would have to invoke to describe the situation appropriately, so that it's more efficient to derive a completely new term from an associated name (e.g. Abelian became such an adjective, which now has its own associations).
It's telling that the author criticizes terms like "Calabi-Yau manifold", but doesn't suggest any alternative: coming up with an insightful name that communicates the key properties of such an object, and is easier to use and remember than "Calabi-Yau" is, let's just say, very very hard.
The same phenomenon is not limited to mathematics. Would Dijkstra's algorithm, the Haber–Bosch process or the Otto cycle be easier to learn and remember if they had snappy, insightful names? Probably. But the same concerns apply. It's hard to come up with genuinely better, more descriptive names for these processes. And even if we were successful in popularizing newer, better names, we would find that the names were not the real bottlenecks that made computer science, chemistry or mechanical engineering difficult to master.