Static, low-js, HTML tags used-as-intended, some basic CSS for formatting, responsivity and dark/light. Modern-looking accessible webpage from scratch done in half a day.

Btw, https://github.com/lyoshenka/awesome-motherfucking-website

[–] [email protected] 32 points 5 months ago (1 children)

The irony of some dude trying to prove a point that a website doesn't need to be bloated and burdened with all the design and fancy scripts, just for other people to incrementally built on top of that idea, one-upping each other in the process, mimicking the exact evolution of the modern bloated website as we know it.

[–] [email protected] 11 points 5 months ago (2 children)

From one of them:

"You're a fucking moron if you use default browser styles."

Or just change your browser settings (they shouldn't be ugly by default).

[–] [email protected] 7 points 5 months ago

You have a problem with Mosaic Gray?

[–] [email protected] 6 points 5 months ago* (last edited 5 months ago)

Honestly I hate the fact that browsers' default CSS exists. The person doing the frontend should have to specify their "default" CSS before the website even loads. I say this as both a user and a programmer, the same website shouldn't look different or break on different browsers unintentionally due to the browser's CSS, and I as a developer shouldn't have to rely on reset sheets to try to patch that.

Everything would be better if it were swapped around, instead of picking out a reset sheet for a site you pick out a default style...

The world would also be better if browsers rendered pugjs/slim and scss/sass and those were the default rather than html and css but I digress...

[–] [email protected] 29 points 5 months ago* (last edited 5 months ago) (1 children)

If we assume "half a day" is 4 hours, and 500 pounds. That's 125 pounds per hour. Which isn't the worst rate. Assuming it's actually capped at 4 hours and we all know that if it's your dad's friend, this is not going to be a set and forget kind of thing. So that 4 hours quickly becomes 10. And suddenly you're down to 50 pounds per hour. And then if it's actually static and simple and good, you still have high odds of getting insane feedback demanding changes to make it worse. A motherfucking website would actually be the best option, but wouldn't get you paid. At that point youre just doing it for the lols.

But ultimately, this isn't even about the rate or how much time this will take. this whole scenario depends heavily on the son here. Is the son unemployed and living in dad's basement for free? Then yeah. Sorry, he should probably take any work he can get for any rate he can get. His dad gets a lot more say in how things work financially if the son is relying on him financially. But if the son is already working a full time job and living in his own house? Then no, I don't care what the rate is. Don't commandeer other people's time. Don't make deals that people haven't agreed to. Come to me with opportunities, not demands.

[–] [email protected] 12 points 5 months ago (1 children)

Yeah, sorry, i couldn't resist to hint on how ridicolously overengineered most professional webpages are.

[–] [email protected] 8 points 5 months ago

https://theoatmeal.com/comics/design_hell

You're not wrong, but a lot of time those webpages aren't overengineered because the developer wanted it to be, but because the client kept making more and more demands.