If devs would use a font stack of maybe Helvetica Neue, Arial, Helvetica, ... this would not be such a problem but a lots of devs (working on osx) do not even care to test on Windows. So actually I find this quite a reasonable approach.
Maybe similar to some browsers (like Opera did before being blink or IE-Spartan) implementing css props of "other" browsers prefixes (-webkit ;) just because devs are "lazy".
I guess a realistic view of how the web is which may be seen :) or :(

Jonathan Snook said on February 06, 2015

@LLULL to clarify, if Helvetica is not installed, Windows will supply Arial when Helvetica is requested.

Eric A. Meyer said on February 09, 2015

I think this is the same as http://meyerweb.com/eric/thoughts/2013/03/12/helvetial/, except maybe from the other end. I’m having trouble keeping track of all the moving pieces at the moment.

Luke C. said on February 23, 2015

I thought that Helvetica was decent (even on PC) except at very small sizes. I always made sure to use Arial when you were under ~ 13 pt or so... and I thought PCs only replaced it for smaller sizes. Arial's uppercase 'R' is enough to bother me at any larger size.

Martijn said on February 24, 2015

Did you know you don't have to quote font names that have a space in them? Now you do :)

James said on April 15, 2015

That's an interesting find. So the best practice then is to declare the Windows specific fonts first rather than the Mac ones.

Sorry, comments are closed for this post. If you have any further questions or comments, feel free to send them to me directly.