Live data from Hacker News

Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts

pixelambacht.nl

151–156 of 156 posts

Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts

#152
post #143
post #90

Earlier quoted context omitted.

A calculator for you, because I'm in pitch-my-side-project mode ;) https://instacalc.com/50060

On A serious note about the UI though, that red/green colour is awful for colourblind people. Didn't even realise there were two colours at first.

Thanks for the feedback. The colors are more syntax highlighting (vs indicating anything important), I'd like to research best practices here. I wonder if there's any client-side settings I can detect to indicate a different stylesheet should load.

Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts

#153
post #152
post #143

Earlier quoted context omitted.

On A serious note about the UI though, that red/green colour is awful for colourblind people. Didn't even realise there were two colours at first.

Thanks for the feedback. The colors are more syntax highlighting (vs indicating anything important), I'd like to research best practices here. I wonder if there's any client-side settings I can detect to indicate a different stylesheet should load.

blue is a good option instead of green. same reason some places in the world have blue, rather than green signals for traffic lights afaik :)

Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts

#154

Wouldn't the most obvious solution be to open-source FA fonts and include them in Linux, Windows, Mac OS, iOS and Android? If they were installed on all systems then we wouldn't really have this issue at all. Given the ubiquity of some fonts this doesn't seem impossible. Or and sorry to say cause I like FA, screw them and see if Apple/MS/Google can have an open standard icon font that doesn't suck.

Doesn't have to be in the OS. Enough to bundle it with the browsers. Same goes for all major frameworks as well, just ship jquery, angular, bootstrap and react with the browser already, like a super long lived cache.

If that's too steep for you, maybe a browser extension would be a good middle ground.

Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts

#155

Earlier quoted context omitted.

Exactly, but I would take it further... It solves a problem that people other than web designers care very little about, but costs me money and creates a slew of other problems... Personally, I wish it was easy to just turn off!

Fonts are a pretty important factor in design. Most people may not explicitly notice it, but it certainly affects the impression they get from a website. You could compare it with http/2: If you do a survey, you won't find many people even knowing it. That doesn't mean it's useless to them.

> Most people may not explicitly notice it, but it certainly affects the impression they get from a website.

Most people already have attractive, readable fonts installed on their computers, which are likely either sensible defaults, or configured for specific reasons (e.g. minimum size to deal with eyesight). Web pages that render as blank white space for awhile, or briefly tease me with text before blanking it out, give me a much more negative impression than ones that simply render in my chosen default fonts.

Re: Saving the Internet 2000TB a Day: Fixing Font Awesome’s Fonts

#156
post #45

Earlier quoted context omitted.

It's one of those things that works "in a perfect world", but in the real world it just doesn't work out that well. For starters, leveraging caching via a common CDN pretty much requires everyone to be using a single version from a single CDN. If you can't agree on that, then every time a new version comes out the web is split and the caching doesn't work, and every time someone decides to use another CDN (or someone…

> For starters, leveraging caching via a common CDN pretty much requires everyone to be using a single version from a single CDN. If you can't agree on that, then every time a new version comes out the web is split and the caching doesn't work, and every time someone decides to use another CDN (or someone provides a new one) the group is split again. All this common web stuff that is distributed by several CDNs (as w…

This is the dream of IPFS.
Post reply on HN