4 ms·
they do have the advantage of being easy to recolor even as an external resource. I personally don't use them and instead use SVGs and there's always the decisi
by asddubs 4y ago
they do have the advantage of being easy to recolor even as an external resource. I personally don't use them and instead use SVGs and there's always the decision of whether to add a bunch of inline svgs, which you can do cool effects and even transitions on for hover effects or light/dark mode, or using external images, which are nicer in terms of separation of concerns, re-use without having to update multiple places and not having graphics buried in the source code somewhere. It would be cool if we could even just have a simple CSS filter that replaces all non transparent parts of an externally embedded image with a single color.
of course there's other benefits like just having to load one file for all your icons, although the tradeoff is also that fonts are messier to update if you're doing custom stuff and not just fontawesome
- toastal 4y agoYou can literally do all of that with SVGs sprites when the fill is set to currentColor.
- asddubs 4y agoOnly with inline svgs, not if they're included via <img>, I believe.
- toastal 4y agoYou can't inline a font as an <img> either?? There are performance benefits to <img>, but generally people recommend <use> for SVGs.
- asddubs 4y agothe point I made in my original post was that a font is already an external resource and doesn't have to be intermingled with the rest of the code.