He also has a very good talk called "Typography for Docs": https://www.youtube.com/watch?v=8J6HuvosP0s
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Columns...
https://www.w3.org/TR/css3-multicol/
It's supported by all browsers. Funnily IE leads the way here, the other browsers require vendor prefixes.
Imagine if we could divide a tab into regions of sites instead?
Having a maximum line length is the humane thing to do, unless the person has phobias of empty spaces, of course. :>
The links you provided are not for the user, but for the designer. Text, however, is a global means of communication, so it should get better treatment, and care in general. Especially by browsers.
Thanks for considering the feedback.
PS: The typographical rule I based 32em on comes from the general rule that, there should at least be room for two alphabets (a-z) on one line. I found 32em to be a sweet spot. The em unit scales in proportion to whatever pixel size you choose for the font, or whatever font size I tell my browser to enforce, so it's highly consistent.
PPS: Another bonus for having a sensible maximum line length, is something I'd never thought about unless it happened to me. It's the nuisance called eye floaters. It's basically an obstruction that floats around in your vision. So whenever the eye moves, the obstruction will dash across your field of view to follow, before coming to rest again. The less the eye has to move in general, the better.
PPPS: For HN (and wikipedia) I eventually ended up making a CSS rule that would override the width of various sections, to comply with the human inside. It's just that there is no line-length attribute, so it must be hacked together specifically for each trouble site.
Both HN, and the linked website, could benefit greatly in readability by simply limiting line-length to ~32em for textual information. It's strange that a browser, designed for human use, has no notion of humans in that regard.