Live data from Hacker News

Perfect Motherfucking Website

perfectmotherfuckingwebsite.com

181–190 of 249 posts

Re: Perfect Motherfucking Website

#181

I want to hecking scream. The point of the original website in this chain was not that you couldn't do media queries, or that all of your designs had to be unstyled. It was a gosh-darned satire that showed that even if you did literally nothing , your website would still be responsive and readable and load fast. The fact that it did nothing, that it was just a completely unstyled HTML page was the reason that the jok…

> >I want to hecking scream. Overreacting much? > The point of the original website in this chain was not that you couldn't do media queries, or that all of your designs had to be unstyled. It was a gosh-darned satire that showed that even if you did literally nothing, your website would still be responsive and readable and load fast. The fact that it did nothing, that it was just a completely unstyled HTML page was…

This meme won’t die. Heck, I'm thinking how to build the next version of this site!

Re: Perfect Motherfucking Website

#182

Earlier quoted context omitted.

I took booleandilemma's comment as a joke, but to the broader point, why does a joke page that's smaller than a blog post need a license? Does it add something to the satire, or does it make it funnier? Clearly the original page's lack of a license didn't make it impossible for anyone else to iterate on it. And again, I can't stress this enough, the point of the original page was not that every single addition you co…

https://github.com/LeoColomb/perfectmotherfuckingwebsite/blo...

:) The irony here being that the WTFYWPL license is generally not advised for projects that actually care about making it easy for others to use the code, it is itself a little bit of a joke license used to forcefully make the point that the author doesn't care about the copyright and is not interested in suing people or arguing about ownership.

So it's appropriate in this context, but also pretty easy to argue that 10 lines of code are not a serious copyright threat anyway, and that it's not clear what code on this page is even subject to copyright in the first place, and that the author might have gone all the way and leaned into the fact that you don't really need an entire Git repo with a license for a single HTML page.

Re: Perfect Motherfucking Website

#183
post #79
post #7

From " http://bettermotherfuckingwebsite.com/ " which is one up the chain: > A little less contrast WHY. WHY DO PEOPLE DO THIS. To give this person credit they have at least chosen some sensible values, rather than gone with something that was just about enough on an expensive graphic designer high-contrast monitor and then not tested it on anything else. Leaving the rest of us squinting to try and read text or manua…

> WHY. WHY DO PEOPLE DO THIS. Do you like 400 nits of #ffffff right into your eyeballs? No? Me neither. The alternative is absolute darkness with extremely bright text, which in turn makes it unreadable (if you have astigmatism as I do) and literally causes pain due to the high contrast. Nothing in nature has such an extreme contrast. The only reason anyone would ever use full contrast is if they have a shitty 6-bit…

If white on your monitor is brighter than a "bright white" sheet of paper viewed under the same lighting - or normal lighting if, for some reason, you've decided to work in the dark - you're doing it wrong.

Re: Perfect Motherfucking Website

#184
post #174
post #90

Earlier quoted context omitted.

On a good monitor, the color contrast between #ffffff and #000000 is far beyond the contrast possible in nature. No reflective material can reach those colors or that contrast. That color contrast is perfect for a game, a movie or an image. But you don't want the feeling of something as bright as looking into the fucking sun mixed with the darkness of the deepest starless night. That's just painful, both in light mod…

"Just calibrate your monitor". If only making every monitor calibrate perfectly was so simple. Sometimes you don't have permission or access to even calibrate said monitor. Your talking about nits like every monitor is able to control its nits output, which is certainly not true. Sometimes, you just have a shitty monitor. There are entire communities dedicated to calibrating monitors as I'm sure you are aware, it's t…

I'm not even talking about using a spyder and calibrating it properly, even just manually changing the settings with a printed reference card can be worth a lot (or even by color matching by eye against an iPhone, as those have great default colors). Or even just manually setting the dials until it looks right.

But the reality is that I can't use some websites because they chose to make my experience worse so users with badly produced and badly designed devices have a better experience. We're yet again at a situation where obeying the standard is punished.

Re: Perfect Motherfucking Website

#185
Serious question:

Why doesn't the Firefox "Reader Mode" icon show up for either this or the original website?

Edit: my reason for wanting Reader Mode on the original website is because I'm reading on a bog standard desktop monitor and the long-ass lines are hard to read.

Re: Perfect Motherfucking Website

#187

Earlier quoted context omitted.

> Yes I know the art theory stuff about never using black because it doesn't appear naturally. I think the underlying reasons for that are underappreciated. When you pick #000000 for your text color, people won't see it as pure black anyway. Imperfections in your screen's backlighting aside, your screen reflects the ambient lighting, or, if you're outdoors and pointed the wrong direction on a sunny day, your screen r…

If you want to go into the "pure black" discussion, I liked that article: https://news.ycombinator.com/item?id=24303042

If you want to see natural pitch black, just go into a deep enough cave and see for yourself.

Re: Perfect Motherfucking Website

#188
post #74

I built an antithesis to this: https://lxe.github.io/everywebsite/

> Also you have to click "I Agree" No thanks. My preferred method for removing cookie banners is to just delete the node from the DOM. It works 99% of the time and I don't have to agree to anything. I suspect it's only a matter of time until someone makes uBlock Origin for cookie banners instead of ads. EDIT: Nevermind. It's already part of uBlock Origin.

What do you do when they say that by continuing to use the website, you agree to the use of cookies?

Re: Perfect Motherfucking Website

#189
post #79

Earlier quoted context omitted.

> WHY. WHY DO PEOPLE DO THIS. Do you like 400 nits of #ffffff right into your eyeballs? No? Me neither. The alternative is absolute darkness with extremely bright text, which in turn makes it unreadable (if you have astigmatism as I do) and literally causes pain due to the high contrast. Nothing in nature has such an extreme contrast. The only reason anyone would ever use full contrast is if they have a shitty 6-bit…

If white on your monitor is brighter than a "bright white" sheet of paper viewed under the same lighting - or normal lighting if, for some reason, you've decided to work in the dark - you're doing it wrong.

Pure white on my monitor can't be created by CSS anyway, thank god, that'd be a full 1014 nits and actually is painful to look at.

But this is a general issue - you want to be able to represent extremely high contrast, far beyond the brightness of a sheet of paper in photos, movies, games, etc. But you want a significantly lower contrast for text. Sadly, websites mix both and offer no way to configure them separately.

Post reply on HN