The fuck off contact page

That with its pixel art is styled so beautifully and so hard to read at the same time. Couldn't read it at all. (It's not an eye vision problem, reading pixel fonts just is quite taxing on the brain).

You can turn on anti-aliased fonts by clicking the bottom right hand corner menu button

I had to go back to the page to check that it actually uses pixel font. To each its own I guess. For me the font was barely noticeable.

Interesting - meanwhile, I found it refreshingly easy to read.

Yeah I started to read the article, went into the CSS, disabled the custom font, and continued reading.

Then I went on HN to read the comments, and found out there is a toggle to get an anti-aliased font…

I found it hard too. Perhaps the difference with the other people responding is the size the font is rendered. On my screen, the distance between the top of a "d" and the bottom of a "y" in the body text is 7mm. That corresponds to font size 18 in Word, or 22px in the browser, so basically a chapter heading.

I went in and just… read it? Don’t see the issue with the thing.

I think it will vary considerably depending on the size, resolution, and quality of your display.

Goes to show the difference in preferences people have. I found the pixel font quite nice, but loathe having to read any serif font, even on paper.

What made me switch the default font off was its color fringing, like it was being displayed on a CRT display with poor convergence.

It's pixel-art styled but not pixel-art arted (is that even a word?). The font does not cleanly align on pixel boundaries on non-HiDPI screens thus it appears blurry. In fact, the whole website appears blurry.

Folks, when making pixel-art styled stuff, ensure they are actually sharp on bix-pixels screen. It's not pixel-art if it's sharp only on your macbook.

I read on a 16” MacBook Pro. Size and display quality were not an issue.

I could have read it entirely with the aliased font, but it triggered me just enough for me to disable it (I’m doing web dev these days, so it took me ~5s; if it would have taken me more I would not have done it).

It was surprisingly readable on mobile, despite a considerable amount of wasted display real estate.

Somehow I expected a downvote, but I'm not really clear on why…