The one where an article extolling the virtues of @font-face makes a pretty good argument against it by completely ignoring how it will look for Windows users. (The screenshot appears to help, but check it out in Windows if you have access.) Enabling Cleartype — not enabled by default, not even there as far as most users are concerned — helps, enabling “standard” aliasing just makes it worse.
I fail to see how this technology is going to be any different from CSS 3*, or HTML 5, or even plain old CSS 2: fucking mind-blowing in the right hands, and a complete, unmitigated disaster in everyone else’s. So basically, all the web designers and typography nuts will have awesome looking websites, some other people’s websites will be a disgusting mish-mash of Roman, Blackletter, all caps, small-caps, monospaced and unlicensed fonts, and everyone else will continue to use Verdana or Helvetica.
Net gain: ?
* Ragdoll pointed out that @font-face is actually part of CSS 3. My mistake.
This post's short URL is http://tumblr.com/xox277h9b
This theme isn't yet complete, because I'm lazy. Don't mind the rough edges, and the unexpected appearance of this message at the bottom of the page.
