2 ms·
I dunno. On OSX in Chrome, at least, they look absoutely identical except for the 'fi' ligature, and the "E" in "Etiam" is kerned one pixel tighter, and there a
by crazygringo 13y ago
I dunno. On OSX in Chrome, at least, they look absoutely identical except for the 'fi' ligature, and the "E" in "Etiam" is kerned one pixel tighter, and there are maybe 3-4 other spots where there is 1px difference of kerning.
I've got a sharp eye, but at 300k for Brick, vs 92k for Google Fonts, I've got to go with Google Fonts here, especially when I'll usually have a given Google Font cached anyways, so it's often 0. But I'm glad to be given the option, regardless, and the opportunity to compare.
And as for character sets, Google Fonts lets you pick the character sets you want, too. Does Brick provide any characters which Google doesn't allow you to add?
- alfredxing 13y agoOSX seems to do a good job at rendering fonts. EB Garamond, at 300KB, is the largest font in the catalogue right now, since its character set is huge (the other fonts are around 80-100KB). And while Google does let you choose character sets, not all special glyphs are included (for example, ornaments). But I agree with you: choice is everything, and it's always better to have an alternative.
- bjxrn 13y agoSpeaking of the cache and download sizes, when I reload the Google specimen the font files return a 304 (not modified) status while the Brick ones return a 200 code and have me download the files all over each time. So for me it's 300k each time the page loads (Brick) vs 92k for the first page load and ~0 each time after that (Google). Is this just me?
- mineo 13y agoExcept for the `fi` ligature and the thing with the Q, they look the same in Firefox on Linux as well.