[MBCook]

I tried to read the article but I couldn't. It's all one big <pre> block. The word wrapping is wrong on input! Individual paragraphs are groups of individual lines and extra long lines that the browser wraps for you. So you end up with lines in the middle of paragraphs that only have one or two words.

Net result is it's very hard to read.

I tried Safari's reader mode, but that was even worse. Because all formatting comes from happenstance in the <pre> tag reader mode loses all formatting. The entire article (and code!) becomes one long block of text.

I'm continually amazed at people's attempts to reinvent text layout in the browser.

[incepted]

> I'm continually amazed at people's attempts to reinvent text layout in the browser.

Agreed.

I don't recommend you try to read pg's essays, they will make you very angry.

[manigandham]

Why is this downvoted? It's true that this blog has bad formatting considering how simple it is, there's no reason to use <pre> for the entire text.

Just because the author created Redis doesn't mean the site isn't badly designed.

[MBCook]

I make these kind of comments every once in a while. They're usually downvoted, I assume, for being off-topic or unnecessarily harsh ('We might have cured cancer!' vs 'I can't read the article because of the video behind the text.').

But I hope some people see them and work on the issue.

Sometimes, if enough other people agree, these kind of comments get voted up. I guess this issue didn't annoy most people enough to get the up votes.