> If your text hits the side of the browser, fuck off forever.
http://stylebot.me/styles/9425
Hrm... CodePen? Sure:
It loaded quickly, and it was a pleasure to edit. I liked it much better than writing tons of JS based on big web frameworks that often had bugs or non-obvious functionality.
Even with the small college blog, though, the CSS was a bit much. The fact that sites like this exist: http://howtocenterincss.com/ seems like a testament to the idea that CSS is a bit broken.
> yes, I know...wanna fight about it?
I use NoScript and RequestPolicy (for the moment incompatible with latest version of FF).
I maintain a site (for a loose definition of "maintain", I suppose) called http://fuckingblocksyntax.com. It's wildly popular in the Objective-C development community, due in no small part to the memorable domain name. But the site itself doesn't contain profanity or over-the-top machismo bravado, and there's a safe-for-work mirror URL at http://goshdarnblocksyntax.com.
A little profanity goes a long way.
I'm never paying for this website again.
And, more importantly, it makes the whole thing much more eye-catching. It's a fun way to a deliver a message - as a vitriolic, spit-flying rant. It would be ineffective if it was friendly and delicate.
Depending on the company, swearing might not be tolerated at all. At my company it's fairly common, but I only do it when in meetings with people I'm fairly comfortable around (my team, my manager, people I commonly work with).
Give it a "margin: 1in" and that'd be perfect.
I love simplicity.