Why using Fonts as Icons can prove tricky: Subpixel Aliasing and Webkit
blog.woop.ie
blog.woop.ie
For small icons, you really want to tune every pixel. Vector sounds great in theory (infinitely scalable!) but it just ends up being a blurry mess at small sizes.
Render the whole shebang twice (including the background), once with "subpixel-antialiased", and once with either "antialiased" or "none". The latter should be in a div in front of and aligned with the subpixel version, and with an `opacity` value of your choosing, probably somewhere around 80%.
Edit: Maybe closer to 60%.
For every negative (so far, just one or two) point against @font-face, I can find 2 or 3 positive, more important points. Creating time-wasting sprites with multiple colors and then a giant section in my stylesheet aligning all of these "icons" is bullshit compared to the simplicity of @font-face.
If this anti-@font-face banter is by purists, you don't really understand what a purist is, or your definition is wildly obsolete.
I don't think he is saying not to use them. In most cases we just want the icons to look "good" and it doesn't matter if there's subtle differences in anti-aliasing. But other times a designer may want to be pixel-exact, in which case sprites still serve a purpose.