A Motherfucking Website
motherfuckingwebsite.com
motherfuckingwebsite.com
I can't even file a damn claim with my insurance on StateFarm.com because some dev had to itch some javacraptasic urge.
It acknowledges that the problem space is difficult. Making something truly delightful is no small task — and it responds by giving up. The site is a (forceful) shrug.
There is absolutely the side of the internet you're talking about, regarding making things pretty, but it's secondary in my opinion.
Youtube used to let you scroll through the list of related videos and read comments while keeping the video you were watching anchored. That's a regression in terms of usability and thus a regression in terms of "art and style".
And bad art and bad style can prevent the spread of information. Remember Hippocrates: first do no harm.
"I'm not actually saying your shitty site should look like this. What I'm saying is that all the problems we have with websites are ones we create ourselves. Websites aren't broken by default, they are functional, high-performing, and accessible."
I.e. the site is explicitly saying it's not trying to argue every site should actually taste like chicken and broccoli, rather it shouldn't lose so many of the good things a chicken and broccoli site already accomplishes out of the box in being different.
I've never really liked the delivery of that message but at the end of the day it's a good message and can't be boiled down to "make your site bland".
>Websites aren't broken by default, they are functional, high-performing, and accessible. You break them.
Meta: is this for the town in Spain or the street in Toronto?
Sometimes nothing is the best thing to do, especially given all the examples that people have decided to do 'something' and it ends up much more than this site.
This is all well and good but it should come after being able to load a page quickly that's accessible over a slow connection and isn't wasteful of metered connections.
<!-- yes, I know...wanna fight about it? -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
...New snipped was designed to break Adblock Plus, which was unable to block inline scripts (and simple blocking analytics.js caused js failures in the same script block). So it was malicious dark pattern. Obviously eventually it was bypassed, which required fake replacements like https://github.com/gorhill/uBlock/blob/master/src/web_access...
However:
- The <meta charset> command should not be needed, if the text is only ASCII anyways.
- The <meta name="viewport"> command should not be needed, if they use the simple HTML as this anyways (without CSS); the client should ought to set it automatically according to the user-defined window size.
- They even have a <script> command (with Google Analytics), which also should not be needed. They have a comment if you wanna fight about it. (I have scripts disabled.)
Isn’t this entirely dependent on what the purpose of the website is? If i am visiting a website to learn about different types of flowers, for example, I sure hope there are some pictures of flowers on it.
However, sometimes it might help if you can specify which ones are merely for decoration and what is what, that you can easily disable them and to avoid downloading them. (Even if a picture is meant to be a significant part of the document because it is what it is about, then you still might not want to download it right away although it would help to display a placeholder (e.g. a hyperlink) in that case.)
<meta charset="utf-8"> means not assuming the default encoding of the client at all, not that ASCII would be invalid given the site's content.
Edit: Forgot <meta name="viewport" content="width=device-width, initial-scale=1">, you probably want this even without CSS. What the client ought to do and what the client does do are different stories and neither are guaranteed to be what you want in the end anyways.
Supporting unencrypted connections does not imply that the client is required to use them.
> What the client ought to do and what the client does do are different stories and neither are guaranteed to be what you want in the end anyways.
Yes, which is why the reader should configure how they intend it to be and the document author should not prevent it from working how the reader intended.
In principle I agree on how the user agent should behave, in practice leaving viewport as default doesn't necessarily match what the user wants or what the developer wants. E.g. user zoom settings are still applied after the viewport scale setting, just now in a consistent way across mobile devices.
The social engineering potential is limited only by imagination.
https://motherfuckingwebsite.com/ (original)
https://web.archive.org/web/20240629092320/http://bettermoth...
https://evenbettermotherfucking.website/
https://bestmotherfucking.website/
> Shit’s finally lightweight and loads fast;
The original does it better. (If JavaScripts are enabled, then the <script> command might make it slower but you can omit that. Fortunately, this "perfect" one does omit the <script>, at least.)
> Finally fits on all your shitty screens;
Not very well. With a small window size, the font is too big and it doesn't fit. With a big window size, it wastes space. The original, without CSS, allows it to fit to the window size appropriately.
> Finally looks the same in all your shitty browsers;
It is better not to; it should look correct in all of the browsers but that does not mean that it should look the same. User preferences, considerations having to do with the display (e.g. mono vs colours), available fonts, accessibility, computer types, etc, can and should make it different, and the author of the document should not have to worry about most of this (as long as minimal accessibility tags are included where necessary; see below about the HTML lang attribute).
> Won’t bleach your fucking eyeballs at night if your browser thinks you like dark things;
The use of CSS means that it is necessary to make this consideration. Omitting CSS makes this unnecessary.
> The motherfucker’s still accessible to every asshole that visits your site;
Due to the redirection of "http:" to "https:", it isn't.
> Shit’s still legible and gets your fucking point across.
Let the reader decide what is "legible".
> I know you love marginalization, but you should take care of people. The HTML tag doesn’t include the lang attribute in your shitty webpage.
This is a valid point; there are benefits of specifying the language.
> Don’t let improper marks and quotes make their way onto websites because of dumb defaults in applications and CMSs.
The ASCII quotations marks are good enough for most purposes, and are also more portable. However, if you do not want to use them, OK; at least you added a <meta charset> command in this case (which is relevant for this one, so it is appropriate to be included; but the <meta charset> command is superfluous in the original).
> And did you let the browser choose the font? Don’t make me read such text with Times New Roman.
I hope you do let the browser choose the font, according to the font installed by the user. Don't make me read such text with needing to download additional fonts that I don't want.
> And as you’ll never be perfect, let others improve your shit or do what the fuck they want to.
OK.
Actually german engineering have bad design that focuses on user convinence and/or aesthetics.
https://www.youtube.com/watch?v=qU7TJPZ2Tp4
Instead of having the camera just pointing outwards, there's an extra failure mode when the camera doesn't flip out. I seen a BMW with the reverse camera stuck, so it can not retract.
I think that my background is a little too yellow, though.
If you want to improve its looks, you can just remove all the css styling.
Also, since you are using mathjax, it's better to use the dollar signs as in LaTeX, and not all these ugly tags with classes. As a rule of thumb, going from latex to html involves little more than replacing empty lines by <p>, \sections by <h2>, and \includegraphics by <img>.
Are you sure pre-rendering images of the formulae wouldn't be just as effective?
I was assuming giving the images a transparent background, but I don't know what pandoc supports.
My favourite is https://evenbettermotherfucking.website/ but I'm a sucker for actually nice and readable typography.
https://www.amazon.com/Dieter-Rams-Little-Design-Possible/dp... (link doesn't contain affiliate)
<https://www.theregister.com/2018/07/12/broadcom_ca_technolog...>
(Let me know if you're having issues reading that, I myself get a message "Referred from Pen Edward Morbius's motherfucking website" viewing under Firefox.)
What most strikes me is that with ever so slightly more advanced browser defaults the Web could be ever so much more readable. What I'd like to see is a standard set of default page layouts ("article", "overview", "lighttable", "catalogue", "discussion", say) along with a few more primitive elements (notes, equations, interactive tables with some basic spreadsheet functionality,[1] and threaded discussions most principally) which could address a huge chunk of what's now highly-styled, and often unreadable, Web designs.
The one thing I find not entirely universally suitable from my design is that the off-white / off-black background/text are not ideal for e-ink devices, though the overall effect remains generally readable.
Gwern's own website (<https://gwern.net/>) strikes me as one of the absolute best highly-styled websites, and absolutely stands out amongst that class.
________________________________
Notes:
1. The ability to sort by specific columns, summarize quantitative columns by total and some univariate statistics (min, max, mean, median, mode, standard deviation), principally. Perhaps the ability to drive a graph based on selected columns as well.
I haven't built it yet because all the frontend frameworks suck still.
Maybe Astro? I don't know yet. I continue to renew the domain in hopes that something will come along.
Alpine.js + htmx, livewire, hotwire, etc maybe. But none of the others really fit well.
https://news.ycombinator.com/from?site=motherfuckingwebsite....
The 2013 submission survived:
You can probably see that website on Lynx or Dillo and it will look the same.
This is the TLDR message of the site. Generally, the more code you write, the worse web pages get.
You're allowed to swear on the internet, you know.