“58 bytes of CSS to look great nearly everywhere” mkws theme

You're arguing over 58 bytes. If someone just wants a minimalistic page, setting a centered body with max-width is step 1. If you stop after step 1, cool. If not: your page is probably going to look better.

However, there is a marked difference between "the content is centered in the browser with whitespace on the sides" and the browser default "it's on the left with all the whitespace on the right". The first one wins. That _should_ have been the browser default in absence of a stylesheet rel, but CSS was born when screens were majestically tiny and the idea of a 24" widescreen was literally a vapourware joke, so it wasn't, and so it never will.

Default browser styling sucks tremendously for mobile browsers.

Concessions can and be made on both sides, and expecting to be use ever larger and wider screens and expecting to still be able to maxi my ise windows is reaching an inflection point where it makes less and less sense, so docking point from a design which doesn't cater to poor habits is sort of silly.

But what I was actually saying is less to do with the design in question and was more about people letting habits continue past the point of them being useful and sometimes well past the point of being harmful. What spurred my statement could have had nothing to do with some new design (and this isn't the first time I've stated it).

Another way to look at it is that I can and have made this statement in isolation to design, in a discussion that was more about maximizing windows in the general case. Linking it too closely to the design in question would be to miss a lot of the point I was trying to make.

> developer-centricity instead of user

Hardly. The user centric take is mobile, is the majority of all website traffic and I'm not even addressing at all.

What I'm doing is making a case that desktop users actually make better use of their monitors that have gotten larger over time, and not just maximizes windows, and for developers to not assume everyone else maximizes windows.

Most people browse using a mobile device now, so really this is about the dwindling few left that have a personal desktop computer they use. That's gamers, professionals and office workers. I think most of those have already learnt this lesson, that when you need to have multiple programs opened at once, maximizing one isn't super effective.

> Line length too long in the current container width? Divide the text into columns.

Or just maximize for no reason and have room for other windows if you want, or zoom the content, whichever makes the most sense for your current situation. Requiring someone design their site around being able to dynamically expand to multiple columns, and figure out how to make that work well with what may be side menus and any number of other design choices all because a minority (probably a minority of a minority) set of users wants to maximize to their own detriment seems kind of ridiculous.

People know how to zoom. They do it all the time on sites that are legitimately hard to read or when they are having problems (if I happen to be without my glasses I zoom the shit out of sites). The only people I hear complaining about this are developers who expect maximizing to continue to have the same benefit it did a decade or two ago even though everything else has changes, which is why I think it's rich that this is being called developer centric.

So zoom a little if it's a problem? It's a few clicks, or holding a keyboard button and scrolling in most browsers. If it's still easily readable without zooming, congratulations, you've found a site that is easy to have open along side other things. In the meantime, I bet it works well for mobile, which is likely the majority of traffic they'll see, and is often harder to zoom effectively and still retain an effective overall readability experience, since mobile platforms often don't re-flow but just magnify on zoom.

If you try playing a game or movie fullscreen you'll understand

Seems this could use a hyphenation-fix - it's pretty terrible ragged right as is. This should now be possible to fix reasonably with plain css3.

https://stackoverflow.com/questions/8937591/is-it-possible-t...

Sorry for the late response, but I've tested this in all my Chromium-based desktop browsers (including Chrome, Vivaldi and Edge) and they all fail to render it properly, including forcing prefers-color-scheme to light: https://ibb.co/XjNFY2G

Works in Firefox though.

Edit: upon some further investigation, the CSS is inverting the elements correctly, except the html (or maybe body) background from white to black. Chromium seems to not want to do that. Now I'm curious and gonna find out why tomorrow