undefined | Better HN

0 pointsMuehe2mo ago0 comments

> there are weird hard line breaks (an ASCII character) in the wrong places

They aren't in the wrong place, if you view the site on desktop, or mobile browser in desktop-mode (for me at least), or the source, the line-breaks form proper paragraphs. Looks like the host actually delivers HTML/CSS with wrapping rules instead of plain text though, which messes it up for screens narrower than a full line in the file.

But either way, the file remains perfectly readable even with the added line breaks, not like any text is missing or moved.

0 comments

eviks2mo ago

I'm amused by all the plaintext defenders not being able to parse this simplest of the file formats!

> if you view the site on desktop ... , or mobile browser in desktop-mode (for me at least), or the source, the line-breaks form proper paragraphs

Nope. The first paragraph consists of 3 lines (#9,10,11), so has 2 extra linebreaks (both in desktop and source form). The next one is lines #13-21, so has 8 extra linebreaks. Because of that it doesn't reflow properly, so looks bad at most of the screen widths

> not like any text is missing or moved.

It is moved due to linebreaks, here is a simple example: the notation of the numbers is force-moved to the next line instead of being adjacent to the numbers, this hurts your "perfect" readability

> re characters 32 to 126

> (decimal)

There is nothing perfect about readability of the poorly formatted/laid out text! And doing everything "plainly" simply robs you of the ability to reach the expressiveness available even to the cave man

j / k navigate · click thread line to collapse