"A* " may be one of the most un-Google-able algorithm names I've come across, since the {asterisk} is used as a wildcard too. (Edit: and is significant for formatting here too.)
As of this post, Googling "A* algorithm" gives more relevant hits about the algorithm than the experience I had many years ago when I tried to learn about it, but it still uses * as a wildcard so you get various other algorithm pages mixed in there too. Trying "A\* algorithm" seems to yield even worse results, which is counterintuitive to the programmers who are most likely to try escaping metacharacters in queries...
It was first published in 1968 (not sure if the name was established then, didn't read the paper) but there's a paper with "A*" in the title from 1985 too. I'm pretty sure "being easy to Google" wasn't a goal with naming things, back then. :)
Peter Hart (one of the three co-authors of the paper) discusses naming on the talk page, to wit:
> In response to this question about why it's called A* :
The notation is borrowed from the statistical literature. Statisticians use a hat (also called a circumflex) to indicate an estimate for a quantity, and often use a star to indicate an estimate that's optimal with respect to a stated criterion (like, say, a minimum variance criterion). When I (Peter E. Hart) was developing this algorithm and especially the theory behind it with my colleagues Nils Nilsson and Bertram Raphael, we adopted this traditional notation. We used hats to indicate estimates of heuristic functions, and went on to compare any other algorithm, call it A, with our provably-optimal (by the criterion of number of nodes expanded) A*. Hart 02:16, 7 March 2006 (UTC)
My sense is that animated visualizations are good at giving an intuitive sense about performance, but static visualizations are better for understanding how an algorithm works. If I was implementing a sorting algorithm I'd rather have one of Cortesi's visualizations on hand.
As of this post, Googling "A* algorithm" gives more relevant hits about the algorithm than the experience I had many years ago when I tried to learn about it, but it still uses * as a wildcard so you get various other algorithm pages mixed in there too. Trying "A\* algorithm" seems to yield even worse results, which is counterintuitive to the programmers who are most likely to try escaping metacharacters in queries...