Which is pretty unfortunate, because the memory management field has always treated reference counting as a form of garbage collection—because it is [1] [2]. The idea that reference counting is somehow not GC is as far as I can tell a recent one (popularized, I think, by Cocoa and iOS?)
This is not just a semantic quibble, because there are successful garbage collection techniques that combine tracing with reference counting (e.g. ulterior reference counting [3]) to achieve GC, so treating tracing as the only way to do GC makes no sense. In fact, David Bacon observed in 2004 that reference counting and tracing garbage collection are best viewed as just two extremes of a continuum [4], and many "optimizations" that you apply to one scheme or the other are really just moving the scheme you choose toward the opposite pole.
[1]: http://www.memorymanagement.org/glossary/g.html#term-garbage...
[2]: http://researcher.watson.ibm.com/researcher/files/us-bacon/B...
[3]: http://www.cs.utexas.edu/users/mckinley/papers/urc-oopsla-20...
[4]: https://www.cs.virginia.edu/~cs415/reading/bacon-garbage.pdf