So, the million dollar question: is it faster to use these, images/sprites, icon fonts? The trade-off I'm assuming is download/load speed vs. cpu load?
Show HN: Littlebox, a pure CSS icon library – worth continuing?
21–30 of 71 posts
Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#22Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#23The swiss flag should be square.
Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#24Really nice icons, good job ! One suggestion for animated icons: add "animated" and "stopped" states if you didn't already.
Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#25Some of the currencies look a bit off for me: http://i.imgur.com/GhjPBr7.png I'm using Firefox on Arch. I guess it could be something to do with me not having the right fonts installed.
Thanks for taking a look at it!
Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#26EDIT: To the author, the download and email icons are the same. This is fantastic. A feature you might not have realized is that it works well with NoScript users. With font-faces considered harmful[0], these icons can be delivered to the user, vulnerability free. [0] https://hackademix.net/2010/03/24/why-noscript-blocks-web-fo...
I'll take a look back at the email and download icons, good eye.
Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#27Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#28Not if this is anything more than an academic exercise. Nice effort, but SVG and, to a lesser degree, icon fonts, are better for this sort of thing.
Re: Show HN: Littlebox, a pure CSS icon library – worth continuing?
#29So, the million dollar question: is it faster to use these, images/sprites, icon fonts? The trade-off I'm assuming is download/load speed vs. cpu load?
Don't forget about compatibility. You can be reasonably sure that font icons will display the same everywhere. CSS-based icons are all over the map compatibility-wise (display issues across browsers).