Making webpages wrong

_{Tags:
rant}

One of the things that slows me the most when designing most things is the fact that I very often find myself not liking what I already have, and tearing everything apart.

If it happens while programming it is not too big of an issue, I can just comment out the old function, move it at the end of the file and start over again, if I find my new design to be less efficient then I just do the same thing and compare it with the other options, till I exhaust all reasonable ways of doing something.

Making webpages however, is a completely different animal. To begin with you can't really measure your webpage, which is a bad starting point, but the worst part is not that, the worst part is that to make a webpage you need to balance 2 different languages at the same time, HTML and CSS. All those things make finding an optimal impossible, so you have to rely on gut feelings and some other less encompassing meters, like loadtime.

Of course this is a non-issue for the majority of webdevs, because they just ignore quality and any problem in one component they "solve" by just adding more stuff at the other side, this is why they are so affectionately called webshitters.

Anyways, the fact that making a website requires both at the same time is absolutely horrible to learn either if you're as OCD as I am about this stuff, when I was younger I could never ever get a proper page because whenever I changed the HTML I promptly changed the CSS for something that would represent better the new layout, and soon after that I changed the layout so it could be properly styled the way I wanted, then shortly I would discover another place where a different style might look better, and an inconsistency would be created which forced me to start all over again, or the more likely scenario; ragequitting.

Thus trying to make webpages taught me next to nothing about making them, the way I "learned" to make them was not by making webpages, but by fixing other people's messes:

// ==UserScript==
// @name        Template
// @namespace   -
// @version     1.0.0
// @match       website.example.com/**
// @grant       GM_addStyle
// ==/UserScript==

GM_addStyle(`
css {goes: here;}
`)

using ViolentMonkey to fix the CSS of hideous looking websites I use the most is pretty easy, and for quite a while it was enough to satisfy me, but soon it tired me and at some point I just got angry and straight up deleted <head>, taking with it most styles.

If you ever do that it won't take too long for you to realize that not only the visuals of most webpages are fucked up, but the DOM is almost certainly a hideous garbage too.

I think the defining mark of a good website is simplicity, imo a good website should be viewable just as well if most of the styling is missing.

In the end, I can't really say I'm showing by example, this website was made specifically so I could cure my decision paralysis when it comes to posting something online (with no success so far), so I try to be a little less methodical than I would normally be.