Live data from Hacker News

58 bytes of CSS to look great nearly everywhere

gist.github.com

1–10 of 254 posts

Re: 58 bytes of CSS to look great nearly everywhere

#7

What is wrong with browser default styling, and why do browsers ship with something that is wrong?

Browsers ship with defaults that are now 20 years old - there was a cool post here about 8px body padding a while ago.

It's not "wrong" it's legacy.

Re: 58 bytes of CSS to look great nearly everywhere

#8

What is wrong with browser default styling, and why do browsers ship with something that is wrong?

Without max-width the content will stretch across your entire screen, which isn’t great for readability. It’s faster to read when you don’t have to look across your entire monitor and move your neck/head.

Re: 58 bytes of CSS to look great nearly everywhere

#9

What is wrong with browser default styling, and why do browsers ship with something that is wrong?

Default styling looks terrible and is hard to read. Humans are good at reading columns at around roughly 80 characters, while browsers default to filling the whole width of the screen with text, resulting in a column that's hundreds of characters wide. Text also gets easier to read when more spaced out; the default line height makes the text too close together.

Browsers still ship the bad defaults because changing defaults would break existing websites.

Re: 58 bytes of CSS to look great nearly everywhere

#10

What is wrong with browser default styling, and why do browsers ship with something that is wrong?

Nothing is explicitly wrong, but the spacing on lists and headers can look kind of silly. For instance, consider in Google Docs - the headers stack nicely, look clean, and lists have perfect indentation / spacing

Those changes pretty much cover all this does, and it doesn't do a great job IMO. I'd let them get away with "look slightly better than defaults nearly everywhere"

Post reply on HN