Read it. Tanooki is wrong.
Read it. Tanooki is wrong.
In short, my 3 arguments are that: "antialiased" is most consistent with the display in other browsers, subpixel antialiasing looks terrible on light fonts on dark backgrounds, and it's impossible to match certain thin font weights from photoshop designs while subpixel-antialiasing is on.
And if you're trying to be pixel perfect to Photoshop, why aren't you using PNG? Anything else isn't going to work, after all.
But if you're only arguing for white on black, well I guess. But you don't point this out, and white on black is horrid for text anyway.
I first clicked on the article hoping to get an answer for the crappier font rendering in Chrome on Win32. Font rendering is one thing IE still does better than Chrome/WebKit.
Chromium Version 20.0.1132.47 Ubuntu 12.04 (144678)
The various comparisons look the same to me as well, and seem to be clear, no obvious 'fat fuzzy' rendering. Cheap as chips Samsung NC10 netbook.Why do you care how your users are choosing to view your text?