I wish it covered error handling a bit more than just 'exit(EXIT_FAILURE)'. FreeType must have some sort of error code or error message function.
But that's all just minor nitpicking. I like the simple and direct walkthrough of the FreeType API (and promising to include friends from the ecosystem in the future). I hope the blog series will continue!
macOS gets around this be aliasing the hell out of all fonts regardless of manual type hinting (or lack thereof).
> they still don’t get it and continue to insist that “it’s too hard to do it right”
What is wrong with that reply? It _is_ hard to do it correct _and_ quick.
If it were anyone other than Google/Microsoft/Apple, I might accept that. Closing the bug (rather than assigning it to a future unknown release) because it’s “too hard” is ridiculous. It’s a valid concern, the results are noticeable even on hi-dpi displays, and it should be fixed (if not now, later).
Windows land doesn’t have an equivalent movement, they don’t control the hardware and so there is still a lot of 1080p in use.
As someone broadly unfamiliar with text rendering it's not clear to me. An introduction to these points would be very helpful
Also using FreeType, but unlike that article rendering on GPU, with ClearType.
No advanced typography features are supported, though.
gcc `pkg-config --cflags freetype2` -Wall -Werror -o main main.c -lfreetype
Because integrating pango/harfbuzz is so difficult I'm tempted to replace my freetype usages with DirectWrite...