This solution is only useful for Windows and will likely regress the visual fidelity of the font in both Mac and Linux.
This effect is present in this blog post. See http://cl.ly/image/0E1g1Z3F3t31 for example. It's less pronounced with larger font faces, but the aliasing makes the text feel fuzzy rather than crisp. At smaller font weights, it's downright blurry and very unpleasant to read.
I have a Stylish script configured to render "safe" fonts every time I am "forced" to use Chrome. Chrome is also very memory intensive on my machine (4GB RAM anyway!)
This font rendering bug is really such a long running joke on Chrome that it might just end up being elevated into some kind of "this is no bug, this one is a Chrome feature!" /frustrated
fyi, that should be "you're given" and "you're ready"
For some reason, Chrome devs are not in a hurry to implement it.
If you're using Firefox try these preferences out for a full DirectWrite experience:
gfx.font_rendering.cleartype_params.force_gdi_classic_for_families: ''; (delete the string)