Apple Doesn't Design For Yesterday
HughPickens.com writes Erik Karjaluoto writes that he recently installed OS X Yosemite and his initial reaction was "This got hit by the ugly stick." But Karjaluoto says that Apple's decision to make a wholesale shift from Lucida to Helvetica defies his expectations and wondered why Apple would make a change that impedes legibility, requires more screen space, and makes the GUI appear fuzzy? The Answer: Tomorrow.
Microsoft's approach with Windows, and backward compatibility in general, is commendable. "Users can install new versions of this OS on old machines, sometimes built on a mishmash of components, and still have it work well. This is a remarkable feat of engineering. It also comes with limitations — as it forces Microsoft to operate in the past." But Apple doesn't share this focus on interoperability or legacy. "They restrict hardware options, so they can build around a smaller number of specs. Old hardware is often left behind (turn on a first-generation iPad, and witness the sluggishness). Meanwhile, dying conventions are proactively euthanized," says Karjaluoto. "When Macs no longer shipped with floppy drives, many felt baffled. This same experience occurred when a disk (CD/DVD) reader no longer came standard." In spite of the grumblings of many, Karjaluoto doesn't recall many such changes that we didn't later look upon as the right choice.
Microsoft's approach with Windows, and backward compatibility in general, is commendable. "Users can install new versions of this OS on old machines, sometimes built on a mishmash of components, and still have it work well. This is a remarkable feat of engineering. It also comes with limitations — as it forces Microsoft to operate in the past." But Apple doesn't share this focus on interoperability or legacy. "They restrict hardware options, so they can build around a smaller number of specs. Old hardware is often left behind (turn on a first-generation iPad, and witness the sluggishness). Meanwhile, dying conventions are proactively euthanized," says Karjaluoto. "When Macs no longer shipped with floppy drives, many felt baffled. This same experience occurred when a disk (CD/DVD) reader no longer came standard." In spite of the grumblings of many, Karjaluoto doesn't recall many such changes that we didn't later look upon as the right choice.
Helvetica is print font, not a screen font. It isn't optimized for pixel displays, and even on fairly high DPI displays does not look a nice as fonts optimized for them. Screen fonts take account of the pixel grid and get hand optimized to look good on them.
Apple is clearly hoping that they have a high end DPI that can overcome these problems, but it doesn't appear they have. The 5k display is only around 200 DPI, and Helvetica tends to look a bit naff below about 600 DPI at small sizes. Of course it's a little more complicated because they have sub pixel rendering, but it only affects horizontal resolution and not vertical resolution. To counter this they have made the fonts a little larger, but of course that means everything takes up more space on screen.
Everyone else uses screen fonts. Bitstream derived fonts for Linux and Android. Microsoft has Segoe and Meiryo, designed specially for them. Some phones have reached the point where Helvetica will look good, around 450-500 DPI, although the iPhone 6 Plus is only around 400 DPI.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Both Apple and Microsoft have been using ripoffs of Helvetica for decades as their default font. That was what all the cool kids did back in the 1980s - if you didn't want to pay for a font, you paid some graphics artist to design one which looked a lot like it but was slightly different. Adobe bought licenses for the real fonts, and if you were in the printing industry and needed the real Helvetica you could buy Adobe Type Manager (originally for Mac, later for WIndows).
All this announcement means is that Apple has finally decided to pay whomever has the copyright on Helvetica for the rights to use it as their default system font. The bit about "tomorrow" is just marketing spin to make it sound like some awesome new thing, when the font itself was made in 1957.
And yes Apple abandons old tech and adopts new tech sooner than the rest of the industry meaning they're often at the forefront of tech which later becomes commonplace among PCs. You can cherry pick some of their successes (e.g. 3.5" floppy, abandoning optical drives) to make them seem brilliant. Or you could list some of their failures (e.g. firewire, lightning thus far, SCSI on the desktop, PowerPC which they abandoned for Intel) to make them seem like bumbling idiots. Apple isn't a prognosticator. They're making guesses about the future just like everyone else. For some reason people are less likely to remember their failures than with other companies.
Helvetica was invented in 1957, so it wasn't created by Apple either. And no sans-serif font can be "most readable".
Contribute to civilization: ari.aynrand.org/donate
What makes you think professionals are even qualified to make the call? Presumably you're talking typographers, graphic designers, etc - artist types who couldn't construct a proper double-blind study to save their souls.
While that may be true, there have been a LOT of studies on typeface readability and legibility over the past 150 years or so, of varying quality.
After having spent some time reading these studies, I've basically come to the conclusion that we've learned basically nothing beyond three basic facts:
(1) readers don't do well with "weird" typefaces except in ornamental or occasional use -- use something that's close to what reader are used to encountering when they will read more than a few words in the font
(2) bigger fonts make reading easier
(3) unless the font has really unusual features (e.g., some characters that don't look like "standard" letterforms), overall design can usually fix most problems -- i.e., doing things like tweaking size, space between lines, space between words, etc.
The last point is really important. Most discussions of typeface legibility have to do with things like serifs, x-height, size of holes in characters like 'o' or 'p', etc. But as long as the letters actually still have standard shapes, you can usually tweak the size or spacing to make it just as legible.
Beyond that, it's basically personal preference and what people are used to. There are studies that seem to show small effects for everything -- serif fonts are better, except when they're not. Justified text is better than ragged right, or the reverse. (Hyphens are bad, or they aren't.) Double-spacing is necessary, or it's not. Larger spaces after periods or punctuation help readability to a small extent, or they don't make a difference.
Frankly, having read a lot in the literature of typography, I think the problem with most of these studies is that overall design matters most, and I'm not talking about the design of the study (though that's important), but rather the typographic design and use case.
Some typefaces will perform better when spacing is tight, others seem better if more space is available. Some typefaces are good for people with various disabilities or vision problems, but readability may be different for those with "normal" vision. Some typefaces look better than others when a smaller size is used, but people express a different preference when text is larger... or when resolution is varied... or....
Typeface is just one of many elements of proper design. And usually reactions like "Oooh, you simply CAN'T use that font on a screen!" or "No, no, no! That works well for newsprint and headlines, but no one would ever like long text blocks with that!" are just based on what people are used to, not what would actually be more legible or readable.
For example, there are situations where people have come to expect serif or sans serif fonts. Expect people to complain if you don't use the standard choice in those situations. That's not to say one or ALWAYS better than the other -- it's just a combination of what's expected and the other design choices.