It renders with proper anti-aliasing in Firefox 26 and Safari 7 on Mac OS X 10.9.
Perhaps his problem has its roots in his operating system, or rather browser developers' use of that operating system? I admit to ignorance about whether browsers are doing their own font rendering or if they are handing that off to the OS...
Not only does it look OK in firefox for me (ff26, windows 7), but if I CTRL-+ to boost the text size, it always looks antialiased. So the supposition that it renders then scales is false.
You can try opening this icon (http://fontawesome.io/icon/windows/) in all three browsers to test - check for the smallest size. Works fine in Firefox and IE, not in Chrome
The bug suggests that it's Windows-only, and the bug also looks like it saw some activity last month. Has someone tried the --enable-direct-write flag that's mentioned in it?
Back in the day this was some kind of problem in Linux.
I always had to do stuff[1] to get MSWindows fonts to the Linux OS. But I don't think anyone needs to do this anymore. Gotta know more about this person's environment.
I am marking this bug as closed: unable to reproduce.
Really, though, you should do a little more testing before you try to go public like this. This code renders almost the same for me on all three browsers: http://i.imgur.com/fmEhGOB.png
Seriously? There are slight differences, but nowhere near the same extent as evidenced on OP's blog. Really, the only place I can see any difference is on the curve of the C's.
Some difference is to be expected. Google, Microsoft, and Firefox are in competition, after all. Microsoft has the advantage of controlling both the OS and the browser in this case. I would be surprised if IE did not render slightly better. As others have pointed out FF and Chrome look better on other OS's (where IE doesn't even play).
Chrome is a little choppy, but Firefox and IE 11 look exactly the same.
All browsers use hardware acceleration nowadays, so I'm suspecting that something is wrong with OP's graphics settings. Are you running those browsers in a VM by any chance?
I dealt with this after a user complaint last week - The "-webkit-text-stroke: 1px" hack mentioned in the Chromium thread does indeed work, but only for headings. If you use a webfont for body copy, and absolutely need cross-browser support, probably just have to fall back.
Maybe because proper font rendering trapped is behind patents? Chrome and Firefox probably rely on public system APIs. IE probably uses private APIs to render fonts. That's just my guess.
For Firefox at least, this is probably because you are not using DirectWrite - that in turn is probably because you are not getting D3D10 (you are probably using D3D9 or no hardware acceleration), the usual cause of this is due to out of date drivers or black-listed hardware. You can check what hardware acceleration you get in the graphics section of about:support.
If you are not getting HWA, you can try forcing it on by setting 'layers.acceleration.force-enabled' to true in about:config (I would do that in a throw away profile though because it might crash Firefox; that overrides the black list).
When will users learn to upgrade their drivers properly?
EDIT: For everybody who thinks this should be easy, what's the latest version of the NVIDIA drivers on Windows Update? Is it not "version 257.21 or newer"?
To be fair, I think the better question is when will driver vendors learn to have their drivers update automatically? Checking to see if your drivers are up-to-date and installing new ones is a tedious process, and I shouldn't have to do it just to have a usable machine.
Yet another technical step that users should learn to do? Computers should work for users, not users for computers. When will operating system manufacturers learn to not make users think (about things they shouldn't have to care about).
A commenter in my blog suggested to ensure ClearType is enablied in Windows settings - and indeed, I found ClearType disabled. After enabling ClearType the fonts look good in FF and Chrome.
The commenter explained that "IE uses it's own version of Cleartype regardless of system settings, while Firefox and Chrome correctly adhere to your system settings."
I'm running the exact same Chrome on Windows 7. http://i.imgur.com/HTrbetQ.png Are you sure your OS ClearText settings are ok? Edit: nrc's suggestion is much more plausible :)
It renders with proper anti-aliasing in Firefox 26 and Safari 7 on Mac OS X 10.9.
Perhaps his problem has its roots in his operating system, or rather browser developers' use of that operating system? I admit to ignorance about whether browsers are doing their own font rendering or if they are handing that off to the OS...