Originally filed as:

The two methods do mostly the same thing, so one should use another. We can think about enhancing the API for RevisionStore::getAuthorsBetween to be able to exclude some users, not sure that's needed really.

But in code review, this came up:

Hm... This is something I haven't thought through... Before we were making a single query to the user table via a join, and now we're going to fetch all the real names one-by-one. This will probably have a severe performance impact.

Do we need to fix it - probably yes, for pages with large histories the new code will likely timeout. How to fix it - I'm not sure. Ideally we'd make user's real name a user option and have a method for bulk-loading user options. Alternatively, UserCache is capable of batch-fetching user names, but I wanted to deprecate this class.