Font-replacement is a thing now on the internet. Gone are the days of Helvetica, Arial, and like, three other fonts. Now designers, coders, and hacks can add fonts to any web project. Heck, sometimes even for free!
But of course there are always drawbacks. The number of font-files you need is staggering, and the CSS you need to set up borders on the insane. Here’s the best CSS code I’ve seen for that. Then there’s the licensing issues: font’s ain’t free (mostly). If you want to use a good collection of the fonts out there, you have to pay. There are loads of services out there at this point that can serve up almost every possible font you could ever want. Some you pay for, some (like what I use for my own website) are free.
Getting past the pay barrier and the CSS file drudgery, you are left with another issue: rendering. Some fonts, while applicable for the web, have not been optimized. There’s a big difference between a web-optimized font, and a print font that has been released to the web. That is to say the latter look like shit most of the time. This is a major difference between a mac and a PC.
Let me explain further.