Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
1–10 of 156 posts
Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#2Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#3Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#4But, isn't subsetting going to result in users now caching your subset instead of a cached copy of everything? I would think that does more harm than everyone grabbing a fully cached copy once from a cdn.
Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#5Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#6There are some really valid points in here and I dislike the idea of using the whole font when only a few icons are required. But, isn't subsetting going to result in users now caching your subset instead of a cached copy of everything? I would think that does more harm than everyone grabbing a fully cached copy once from a cdn.
Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#7There are some really valid points in here and I dislike the idea of using the whole font when only a few icons are required. But, isn't subsetting going to result in users now caching your subset instead of a cached copy of everything? I would think that does more harm than everyone grabbing a fully cached copy once from a cdn.
Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#8What's the argument against icon fonts? Using actual SVGs?
There are a number of tools that will optimize svg files for size like svgo. Output straight from Illustrator, for example, has a lot room for improvement. I also usually end up hand-tweaking for things like removing the full style and doing that in my site's CSS.
What I think is really still needed are more options besides Illustrator for generating svg content. Yes, Inkscape is overall ok but is lacking in setup ease and genera speed.
There a number of programs that are so close to doing what is needed and then won't save or export an svg. Pixelmater, looking at you.
Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#9What's the argument against icon fonts? Using actual SVGs?
- You're more likely to hit aligment/layout issues because you're using a tool designed for text to render pictures
- The character codes used are textual information but have no semantic meaning (this can be addressed by using ligatures or characters in the private unicode range)
- Adding more icons requires regenerating the font
- Using a subset of icons requires regenerating the font
- Font authoring is non-trivial and requires much more specialized tools and knowledge when compared to SVG
- You need to ship the font in various formats (TTF, OTF, WOFF, WOFF2)
- It's not easy to animate icons, or include colors or transparency
- By now SVG support is sufficiently widespread, so the original rationale for using font icons no longer applies
None of these, except maybe the rendering quality, are deal breakers. Workarounds and counterarguments do exist. And SVG does have some disadvantages too (e.g. parsing overhead, filesize, memory consumption)
I personally side with using SVGs currently. As technology progresses, I might definitely reassess my view.
Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts
#10What's the argument against icon fonts? Using actual SVGs?