I think they must have done, I also don't remember it looking so bad before.

Seeing quite a few sites and blogs now getting a bit careless with CSS @font-face rules and seemingly not bothering to test their sites in Windows.

More on it here: http://blog.webink.com/why-fonts-suck-windows-hinting

Yeah, so many of the Mac designers / evangelists who screamed the loudest about "Designed for IE" and other web evils have come full circle, and adopted a mantra of "Looks good on my MacBook with Safari, ship it!"

Yes, it used to be Proxima Nova served with Typekit.

Ah, thanks for the info, perhaps they should switch back. Looks like they went home-brew to save cash (or to be more unique). Seems wrong to have to use the Readability bookmarklet to read a Svbtle blog!

My browser (FF on Win7) still renders as Proxima Nova.

Yep, it's been changed back. =)

Many web fonts seem to look bad on Windows, I think in part due to many websites being designed on Macs. This one looks particularly bad on Chrome, but Firefox isn't so bad.

Is this an argument for users disabling web fonts? I don't think there are very many situations in which they provide a better user experience. A few days ago we got the "Wikipedia Redefined" article[1] (in which the capital "I" looked like a capital "J"[2]).

I don't think we have to go whole hog and completely ignore designers' intent, but if usability is being compromised I think it makes sense to take advantage of the fact that we're doing the rendering on the client.

1: http://www.wikipediaredefined.com/

2: http://news.ycombinator.com/item?id=4354000