4 ms·
hint: if you write an article about something that is broken and constantly moving by the hour, do not use that thing to document your article. if she didn't u
by gcb0 10y ago
hint: if you write an article about something that is broken and constantly moving by the hour, do not use that thing to document your article.
if she didn't use utf but images (to talk about the rendering) that article would have been something in 4 days, when it will be irrelevant because fonts and browsers will already have changed.
Also, people on the several platforms she dismissed as nobody-cares (android pre 5, linux, windows pre-7, etc) would have had a clue about the subject.
- harrisi 10y agoThis seems a bit harsh. From the article, "I’m going to keep talking about the Apple font, because that’s the code path I worked on in Chrome..." Although this is toward the end of the article, it does give a good reason for why the author is only focusing on a rather small domain: she worked on this specific domain (Chrome, Apple, emoji). In case it wasn't immediately obvious, she doesn't actually mention any browser (or rendering engine) other than Chrome (Blink). Perhaps you were looking for a more complete essay on all things emoji, but it looks more like the author just wanted to write about some stuff she had worked on that she thought was interesting.
- gcb0 10y agoWas talking about presentation not content. for anyone outside the san francisco bubble (ie not using Chrome on a last model mac) this article only shows mojibake. if you want to talk about broken rendering, always take screen shot.