What happens when the community decides this one isn’t good enough and comes up with a replacement? The problem I’ve always had with these descriptive names is (a) they are often hard to google because they conflict with all sorts of documentation about the problem space and (b) when they’re deprecated, they become a trap for beginners. “Cute” project names are better for the same reason as we don’t name children and pets random English phrases describing them.

The replacement can just be called getada2. It worked for Python's standard library (unittest2 and all that).

Or fetchAda or grabAda, english is filled with synonyms.

Imagine if this happened with stream processing systems: “here at Acme Corp we decided that Apache Stream Processing wasn’t nearing our needs so we switched to Apache Creek Processing after evaluating it and Microsoft’s River Processing solution”

Well then surely it should be "UpdAda"?

(I hardly...)

How about "AddUp"?