Hacker News

Favorites Setup
Comment by theandrewbailey | original | Bug Blindness
[−]theandrewbailey · 2026-08-30 Sun 01:11 UTC · link
Bug: this blog has no max-width. Lines of text will grow infinitely long with width.
[−]Conlectus · 2026-08-30 Sun 01:20 UTC · link
For what it’s worth, the author would not consider this a bug. He does it (as I understand) because he distrusts the research on the impact of line length on readability.
[−]lo_zamoyski · 2026-08-30 Sun 02:01 UTC · link
Which brings us to one of the earlier claims

"I easily observe hundreds to thousands of bugs per week"

which should be rewritten as

"I easily observe hundreds to thousands of things that I consider to be bugs per week"

which is to say that the "bug" is in the eye of the beholder. It seems the author stretches the definition of "bug" to include cases where something functions, but in a manner that is open to improvement or not to his taste.

[−]andrekandre · 2026-08-30 Sun 02:15 UTC · link

  > he distrusts the research on the impact of line length on readability.
whats the reason for that?
[−]Cider9986 · 2026-08-30 Sun 04:14 UTC · link
It's less readable for me, never heard of any research. Whatever, there's reader mode.
[−]encomiast · 2026-08-30 Sun 01:21 UTC · link
To say nothing of this bit of markup, which actually raises an exception in the browser:

`<link rel="icon" href="data:;base64,=">`

[−]jwilk · 2026-08-30 Sun 08:24 UTC · link
Curiously, this makes Firefox display the default favicon (instead of no favicon):

https://github.com/mozilla-firefox/firefox/raw/refs/heads/ma...

[−]kmoser · 2026-08-30 Sun 02:04 UTC · link
I had this same discussion on another HN thread a while back. I prefer lines to run as long as possible; I find it difficult/distracting to move my eyes to the beginning of the next line every few seconds. I'm sure I'm in the minority, but I have to believe I'm not the only one out there who feels this way.

Rather than having the website author wrap lines at a width that works for the average user or use case (which may only be optimum for a percentage of users or use cases, which may not include me), the user can simply make their browser whatever width they prefer the lines to wrap at. This way, everybody gets to choose what works for them.

[−]socalgal2 · 2026-08-30 Sun 03:08 UTC · link
> I find it difficult/distracting to move my eyes to the beginning of the next line every few seconds.

You must find it difficult to read books, magazines, newspapers, as all of them have short lines

[−]lmm · 2026-08-30 Sun 07:31 UTC · link
I am in the same boat as GP, and I wonder if it's one of the reasons I migrated hard to ebooks and online magazines/newspapers as soon as that became possible and never looked back.
[−]mrob · 2026-08-30 Sun 10:38 UTC · link
The bad text formatting in printed works (including the bizarre decision to sacrifice useful vertical position cues ("ragged right") to imitate the technique medieval scribes used to reassure their patrons they weren't wasting valuable parchment ("full justification")) is a big reason why I avoid them whenever possible.
[−]hibbelig · 2026-08-30 Sun 07:45 UTC · link
Making the browser windows narrow is a bad suggestion. Because most websites have some sort of navigation bar on the left and another bar on the right, so we need a wide enough window to get enough of the main text (width).

There are very few websites without those columns.

[−]skydhash · 2026-08-30 Sun 02:13 UTC · link
> Bug: this blog has no max-width. Lines of text will grow infinitely long with width

Are you maximizing your browser’s windows?

[−]frabcus · 2026-08-30 Sun 07:45 UTC · link
I do - I much prefer using computers with only one window visible. And use all the keyboard shortcuts (tab, window and desktop switching) to rapidly change what the thing it shows is.

I reckon there's something interesting about human variety in focus and/or visual processing this tells!

[−]layer8 · 2026-08-30 Sun 10:08 UTC · link
I, on the other hand, use the keyboard shortcuts to adjust the browser width to achieve the desired line width and line start, because even when the web page takes care to set these, it varies from site to site and rarely is what I want. (For sites I visit often, I use window manager automation to auto-adjust the browser window size.)
[−]theandrewbailey · 2026-08-30 Sun 11:03 UTC · link
No. I keep my browser to about half of my 27" 4k monitor.
[−]PieUser · 2026-08-30 Sun 02:18 UTC · link
Thank god for Reading Mode in browsers...
[−]Terr_ · 2026-08-30 Sun 02:43 UTC · link
I don't see that as a code-bug but a difference in implied requirements. Namely, the expectation about which person can/should choose the width of the lines everyone had to read.

Let's flip it around: Suppose someone put in code/markup to prevent any viewer from picking a larger or smaller font-size. Would that be "just fixing a bug", or would some of us be pissed that the author has dictated something in a way which infringes on our autonomy and disrespects our superior-knowledge about what constitutes our good reading experience?

[−]nottorp · 2026-08-30 Sun 07:02 UTC · link
Someone always complains about that when a danluu link is posted.

Every time I have to go back to the article (usually after having already read most of it) and notice "yes, it's using the whole browser window".

I think you can obtain the common experience of one sentence per screen and lots of scrolling by pressing ctrl/cmd and plus a couple times.

[−]chrisjj · 2026-08-30 Sun 12:01 UTC · link
By that token every CSS1 page is bugged.