So I was recently talking to my typographer friend Ike about what I believe to be some severe deficiencies in the way that OS X handles font rendering. Now, I'll be the first to admit that I'm no typographer, but I do a lot of software and web development, using my powerbook, a windows computer, and linux. So, it seems to go without saying that I'm not concerned with fonts in print or at large sizes, as much as I am with having clear, legible, type that's easy on the eyes and lets me get my work done.
Now, that said, I should begin by noting that from a legibility standpoint, I've yet to experience a font rendering system or set of default fonts that are better than those provided with Microsoft Windows. (not ClearType, mind you, but the default non-antialiased (at small sizes, anyway) font rendering). Suffice to say I've been happy with developing under Windows (from a font perspective, at least)
Mac OS X, however, is a different story all together. I've noticed some serious deficiencies in the way that OSX renders fonts. I suppose that there are three things about it that really get under my skin:
1) Fonts render too light: Take for example the premier text editors on both the Mac and Windows platforms, BBEdit and EditPad Pro (Because both of these pieces of software use the default system font rendering algorithms, we're not comparing the programs here, but the underlying operating system font rendering). The following two screenshots illustrate the default configurations of both BBEdit and EditPad Pro
. Now, admittedly, the fonts in the OSX screenshot are antialiased, while they aren't in the Windows screenshot, but that aside, I find the windows fonts to be infinitely more legible and usable than those in OS X.
2) Font kerning problems: This problem REALLY confuses me. Partly because of the lack of quality control on Apple's end, but also because I haven't heard people complain about this in the past. Take for example
this screenshot. Taken in Safari, Courier New, 14pt (blue and underlined because it's a link). Being a monospaced font, I would expect the space between the first square bracket and the 't' to be the same as the space between the 'p' and the closing bracket. Also, the underline extends beyond the closing bracket, and there is no space between the underline and the text.
So, are these "bugs" or are they "features"? What does everyone think about this? Are Mac OS X fonts pretty but unusable? Are they ugly? Are non-antialiased fonts better at screen resolutions (72dpi) for programming/scripting than anti-aliased ones? Is this a problem with the fonts themselves or the implementation of the renderer?