Live data from Hacker News

HN: Please replace grayarrow.gif with Unicode character ▲

news.ycombinator.com

41–50 of 190 posts

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#41
post #39
post #3

Very good proposal. There are more unicode symbols to choice from: http://www.alanwood.net/unicode/geometric_shapes.html Down arrow/triangle: ▼ It is not only matter of resolution but I personally like bigger fonts and have zoomed in HN so triangles look bad: http://i.imgur.com/fpA7N.png

I also zoom in to 125%, not sure if it's just me, but for a textual site the default font size seems too small. Maybe my eyes are just giving up. Out of curiosity, I was wondering why the triangle wasn't a CSS triangle.. wouldn't that be more efficient than a gif?

Not necessarily. The gif is requested once and cached, and then rendered once and cached.

The CSS triangle would get rendered over and over again.

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#42
post #39
post #3

Very good proposal. There are more unicode symbols to choice from: http://www.alanwood.net/unicode/geometric_shapes.html Down arrow/triangle: ▼ It is not only matter of resolution but I personally like bigger fonts and have zoomed in HN so triangles look bad: http://i.imgur.com/fpA7N.png

I also zoom in to 125%, not sure if it's just me, but for a textual site the default font size seems too small. Maybe my eyes are just giving up. Out of curiosity, I was wondering why the triangle wasn't a CSS triangle.. wouldn't that be more efficient than a gif?

> for a textual site the default font size seems too small. Maybe my eyes are just giving up.

++, although my eyes are giving up, and getting a high resolution / small screen size MBA didn't help.

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#43
post #20

Earlier quoted context omitted.

The image is only loaded once and does not block anything (in fact it's loaded in parallel with — and the same size as — the orange Y logo at the top-left, and the tracking gif). Furthermore the images on YC have extremely low dynamicity and size, so there's little chance they'll be evicted from the browser's cache (short of a manual cache clear), so their 100 bytes will only be loaded once the first time ever you vi…

The image is only downloaded once, but each page you load re-requests it. If your account has enough karma to downvote posts, you're requesting two array gifs per page view. There's no Expires header being set, so your browser is not caching these images. A full roundtrip to the HN server to get back the "content hasn't changed" status code (304) is required for each.

> The image is only downloaded once, but each page you load re-requests it.

No, it most definitely does not does not.

> There's no Expires header being set, so your browser is not caching these images.

You're out of your mind, of course the browser caches it, the browser caches everything it can by default: http://i.imgur.com/hrmIs.png

> A full roundtrip to the HN server to get back the "content hasn't changed" status code (304) is required for each.

That is not even remotely close to what happens in the actual reality we're part of.

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#44
post #37

And please make the up-vote button larger than the down-vote one. (They're not really logical opposites and their use frequency is quite different.)

How are they not logical opposites? Isn't an upvote exactly the opposite of a downvote?

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#45

Earlier quoted context omitted.

The image is only loaded once and does not block anything (in fact it's loaded in parallel with — and the same size as — the orange Y logo at the top-left, and the tracking gif). Furthermore the images on YC have extremely low dynamicity and size, so there's little chance they'll be evicted from the browser's cache (short of a manual cache clear), so their 100 bytes will only be loaded once the first time ever you vi…

On the other other hand, it takes 83 bytes of HTML to represent the image tag which requests that 100 bytes of image. It only takes a couple of bytes to represent the Unicode character.

Sure, that's a valid point. However considering the HN home page is sent as raw HTML right now, there'd be much better savings by enabling gzip, reducing the home page's over-the-wire size from ~22k to ~5k. Compared to ~2.5k (from 22k to 20k) of savings from removing all 30 instances of the image tag.

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#46
post #6

Excellent idea! Now if we could only convince w3C that the entire Unicode Symbol Set deserves names and not hex or octal then I'd be very happy indeed ♞ should be bnight and so on...

No, I don't think it's a problem. I believe HTML only had symbol names because of incompatible character sets, allowing Unicode characters in ASCII and other encodings. But modern text editors and sites can use Unicode symbols just fine, why avoid them?

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#48
post #38
post #36

I’m more concerned with the lack of DOCTYPE and old-school HTML.

Really? Those are completely irrelevant to me and I have no idea why anyone would care as long as the site functions. It's not ideal and I wouldn't encourage it but does it really matter?

Yes, the current system is inefficient and very outdated considering this is a site largely about startups

Re: HN: Please replace grayarrow.gif with Unicode character ▲

#50
post #29

Using Unicode shapes and vector-based icons is a great step forward. They're not suitable for every use-case but for most purposes they work well. Lately I've been using Font Awesome[1] to a great extent. Is there a tool that lets you simulate what a site would look like on a high-DPI/Retina display? Is it simply enough to zoom the page in to get a feel for it? [1] http://fortawesome.github.com/Font-Awesome/

Could you give us some use-cases where it's not suitable? Thanks :)

In addition to what coderdude said, not everybody has a browser that supports custom fonts, or has custom fonts enabled, so if your site depends on custom font glyphs for navigation you could be making it unusable.

Sticking to glyphs that are part of standard Unicode should be fine - those should render no matter what font the browser happens to use by default.

Post reply on HN