The main drawback with the page's unstyled design is that the page is not mobile friendly.

Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.

xnx 2 hours ago | parent | next [-]

Having that not be the browser default was a good idea in 2008, but not now.

▲

zahlman 32 minutes ago | parent | next [-]

I don't have a smartphone to test on. What happens without this?

	▲	xnx 8 minutes ago \| parent \| next [-]
		If you want to see it for yourself: https://developer.chrome.com/docs/devtools/device-mode
	▲	oakesm9 27 minutes ago \| parent \| prev [-]
		You essentially see the desktop version zoomed out by default with tiny text. You need to zoom in, but the line length is still desktop sized so you need to scroll left and right as well as up and down to read it.

▲

account42 2 hours ago | parent | prev [-]

It wasn't a good idea even in 2008.

▲

recursive an hour ago | parent | prev | next [-]

This sounds like a critique of mobile browsers. Make friendliness the default!

▲

burkaman 2 hours ago | parent | prev | next [-]

It's obviously not designed for mobile but I wouldn't call it unfriendly, it's still fast and pretty easy to read. It also works perfectly with Firefox reader mode.

▲

childofhedgehog 34 minutes ago | parent | prev | next [-]

What part of this is actually not mobile friendly? I’d argue this is laid out pretty well compared to some websites that are “mobile friendly” but load poorly or make it impossible to scroll.

▲

Krssst 2 hours ago | parent | prev | next [-]

Firefox's reader mode works really well on the article, I wonder why it's not the default for unstyled pages.

▲

barbazoo 2 hours ago | parent | prev [-]

That's a feature for me, not a bug. Not everything has to be everything-friendly all the time, especially if it makes it easier to consume content or stuff.

Edit: I'm forgetting about certain accessibility issues, although I'm not sure this plain page isn't a good fit for accessibility tools.