4 ms·
No hinting.
by ggm 7y ago
No hinting.
- cerberusss 7y agoYeah, that's what the developer mentions in the readme. I wonder though, is it such a big deal in the era of 4K displays?
- jfkebwjsbx 7y agoWe are quite a few years away from the 4K era. 4K desktop displays are still a blip in the radar (about 1%).
- cerberusss 7y agoI didn't realize that the percentage is that small! However now that I think about it, mobile could be an excellent place to use this library.
- jfkebwjsbx 7y agoIndeed, for mobile there is a good case!
- fsloth 7y agoNeither does OS X Quartz.
- sjwright 7y agoMy understanding is that the macOS font renderer uses limited hinting for small pixel sizes. Of course retina displays mean most normal on-screen text is rendered at 16px or larger, so it's increasingly rare for hinting to matter.
- solarkraft 7y agoDoes this mean Mac OS doesn't have it at all?
- ggm 7y agoNo, just not quartz. Microsoft and OSX have some share in hinting
- montroser 7y agoWe are finally in the future where hidpi displays mostly make hinting unnecessary. Even before now, hinting has been a highly questionable pursuit. I believe Freetype enabling its autohinter by default has led to ~20 years of most free software having tortured, ugly misshapen text.
- Someone 7y agoI don’t think you can blame TrueType’s hinting for problems with FreeType’s autohinter, which was created specifically as a patent-free replacement for TrueType’s hinting (https://www.freetype.org/autohinting/hinter.html https://www.freetype.org/autohinting/hinter.html)
- montroser 7y agoThe autohinter was a noble attempt, and in some cases it eventually did a passable job. But enabling it by default is the part that I think might have been a mistake.