Slashdot Mirror

Seven CSS declarations improve its readability.

Yes. Some people just want an MFing website. Others are willing to spend an extra 151 bytes on making it readable.

Even showing and hiding replies can be done without script in 98 percent of browsers, using a small amount of CSS3 to restyle a checkbox.

And then someone adds six lines of CSS to make it more readable, resulting in a better MFing website. (The one thing I disagree with on Better is "A little less contrast".)

Every single time I make a web site, I dread fighting with the limitations of HTML and CSS, especially when I can't just require the latest and greatest browsers.

Has it occurred to you that you're the problem here, not the browser?

Here's a http://motherfuckingwebsite.com/ renders just fine on Lynx. If you want to use CSS, you can also make a http://bettermotherfuckingwebsite.com/ that renders well on every browser written in the past 20 years.

Whatever happened to failing gracefully? I've been using the web since the days of "This Page Best Viewed At 800x600 In IE4 / Netscape 3". The problem, then as now, isn't the browsers, it was the web designers who decided to implement everything in Flash and Java because HTML 3.0 wasn't fun enough.

Your summary is great! But I'm lost on one point so would someone be kind enough to describe what http://motherfuckingwebsite.co... does? I'm at work so visiting that site, searching for it, etc. will not do.

It uses HTML 3.0 tags (there's a http://bettermotherfuckingwebsite.com/ that demonstrates good usage of CSS) to create a fully responsive, cross-platform web experience, aka., a motherfucking website.

This is a motherfucking website.

And it's fucking perfect.

Seriously, what the fuck else do you want?

You probably build websites and think your shit is special. You think your 13 megabyte parallax-ative home page is going to get you some fucking Awwward banner you can glue to the top corner of your site. You think your 40-pound jQuery file and 83 polyfills give IE7 a boner because it finally has box-shadow. Wrong, motherfucker. Let me describe your perfect-ass website:

• Shit's lightweight and loads fast
• Fits on all your shitty screens
• Looks the same in all your shitty browsers
• The motherfucker's accessible to every asshole that visits your site
• Shit's legible and gets your fucking point across (if you had one instead of just 5mb pics of hipsters drinking coffee)

Well guess what, motherfucker:

You. Are. Over-designing. Look at this shit. It's a motherfucking website. Why the fuck do you need to animate a fucking trendy-ass banner flag when I hover over that useless piece of shit? You spent hours on it and added 80 kilobytes to your fucking site, and some motherfucker jabbing at it on their iPad with fat sausage fingers will never see that shit. Not to mention blind people will never see that shit, but they don't see any of your shitty shit.

You never knew it, but this is your perfect website. Here's why.

It's fucking lightweight

This entire page weighs less than the gradient-meshed facebook logo on your fucking Wordpress site. Did you seriously load 100kb of jQuery UI just so you could animate the fucking background color of a div? You loaded all 7 fontfaces of a shitty webfont just so you could say "Hi." at 100px height at the beginning of your site? You piece of shit. It's responsive

You dumbass. You thought you needed media queries to be responsive, but no. Responsive means that it responds to whatever motherfucking screensize it's viewed on. This site doesn't care if you're on an iMac or a motherfucking Tamagotchi.

It fucking works

Look at this shit. You can read it ... that is, if you can read, motherfucker. It makes sense. It has motherfucking hierarchy. It's using HTML5 tags so you and your bitch-ass browser know what the fuck's in this fucking site. That's semantics, motherfucker.

It has content on the fucking screen. Your site has three bylines and link to your dribbble account, but you spread it over 7 full screens and make me click some bobbing button to show me how cool the jQuery ScrollTo plugin is.

Cross-browser compatibility? Load this motherfucker in IE6. I fucking dare you.

This is a website. Look at it. You've never seen one before.

Like the man who's never grown out his beard has no idea what his true natural state is, you have no fucking idea what a website is. All you have ever seen are shitty skeuomorphic bastardizations of what should be text communicating a fucking message. This is a real, naked website. Look at it. It's fucking beautiful.

Yes, this is fucking satire, you fuck

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. You break them. You son-of-a-bitch.

• "Good design is as little design as possible."
  - some German motherfucker

What's your download speed? I can browse most of the web pretty painlessly

The download speed isn't the problem. The rendering speed isn't even the problem. The problem is multiple DNS lookups and TCP/IP setup/teardowns for craptons of, well, crap that add no value to the content in the first place.

Web "developers" need to stop fucking around with the latest framework and just build a http://motherfuckingwebsite.com/, and if that's not good enough, they can just build a http://bettermotherfuckingwebsite.com/.

Chromium (which IS open source) apparently has build issues and isn't even in the normal Fedora repos.

Fedora's fault. In Xubuntu, a Debian derivative, all I have to do is sudo apt-get install chromium-browser.

There was a time not very long ago when Chromium was not available in ubuntu official repositories either, and you had to install it yourself or use a PPA... just like Ubuntu you can get chromium running on Fedora. The reason it's not in their official repositories is more an ideological one, supposedly the packaging of customised dependencies rather than integrating more naturally with the ecosystem goes against the ideals of whomever has authority over what does and does not go in the official list.

I like the chromium project and use it as my main browser, i like the developer community also who are super fast at fixing bugs, but i also understand that it's a very large and far from an ideally designed collection of code, modern browsers are hard and i guess the more pragmatic work-in-progress approach is a better fit for Ubuntu.

And the memory footprint of all browsers is crazy now.

Is this the fault of the browser or of the sites you visit? Back when sites weren't as image- and script-heavy, like Better MF Website, a graphical browser could actually fit on a 16 MB machine. Nowadays sites are covered with carousels full of high-DPI photos, plus developers think they still need jQuery and all its bloat just to get the site out the door faster.

Sure, but modern browsers are definitely memory hungry... i'm a chronic single tasker, i currently have one chrome tab open, the browser was started fresh and navigated to slashdot, summing up the memory footprint of chromium tasks it's taking up around half a GB to view this page, seems a little heavy, and i don't think i can blame all that on this one slashdot page.

Chromium (which IS open source) apparently has build issues and isn't even in the normal Fedora repos.

Fedora's fault. In Xubuntu, a Debian derivative, all I have to do is sudo apt-get install chromium-browser.

And the memory footprint of all browsers is crazy now.

Is this the fault of the browser or of the sites you visit? Back when sites weren't as image- and script-heavy, like Better MF Website, a graphical browser could actually fit on a 16 MB machine. Nowadays sites are covered with carousels full of high-DPI photos, plus developers think they still need jQuery and all its bloat just to get the site out the door faster.

I also don't appreciate them throwing unnecessary crap into the browser like the web developer stuff

Browser developers distribute the debugger with all copies of the browser to keep sites from intentionally detecting a debugger's presence and stopping working if one is found. If everyone has a debugger, the site operator can't block people who want to tinker, learn, and make a site more usable without blocking everyone.