



I don’t know many people that still customize their Browser default style sheets (can you even do that in Edge, I wonder?). Of course when the web first started, the idea was that it would serve styl able but-unstyled-by-default content _and then the user would style it as they liked_ so they could enjoy a consistent and customized experience no matter what they were browsing. While modern CSS has been inching towards becoming Turing complete (is it already now? I think so long as adding html elements via :before/:after remains disallowed we aren’t there yet?), CSS’ biggest saving grace is that it was a declarative and Turing incomplete. And neither one of those interferes with text only, thank god. Once you embrace minimalism, you realize that aesthetics are primarily a concept of white space and typography. Text-only doesn’t have to be _ugly_ though. My first, knee-jerk reaction was “God, that loaded fast!” even though I already knew going in what to expect.
