Why you shouldn’t need to use validation as a building tool anymore (until you do).

I was watching Dan Cederholm talk about Hand Crafted CSS, and the 4th point he made was about when validation matters.

He basically described that validation is helpful for checking why the site isn’t loading the way you want. So it’s useful for finding markup errors like close tags. Fair enough, if you are still writing HTML by hand, but a tool like HAML completely (or as close as possibly) protects you from markup errors like close tags. It also happens to make writing html twice as fast or more (just add a tag at the top and indent and you have wrapped a whole section or code.

So here’s the analogy I came up with to explain to my wife:

If I were laying railroad track, and using old wooden rail ties, I’d want to measure the width of the track every time I went to drive in a new spike, because obviously if the width of the track weren’t standardized, trains would fall right off. Using HAML* is a bit like ordering pre-cast concrete railroad ties, and instead of having to measure each time, I just have to line the track up into the groove, and bolt it down.

The only time I might run into a problem is if someone ordered rail ties for the wrong standard, which would be a bit like if you used a poor or broken HAML interpreter. On the plus side, with HAML—as opposed to railroad construction—fixing the interpreter can be done retroactively if needed.

So we really shouldn’t need to waste time building an XHTML structure validator for HTML5, because we shouldn’t be hand coding HTML5 the way we used to. But those are just my 2 cents.

Still, the video worth definitly worth watching, I’m at the very least, going to load more of my pages without images and see what happens

Also http://dowebsitesneedtobeexperiencedexactlythesameineverybrowser.com/

Or Markdown, or LaTEX, though I think HAML gives the right mix of craft (you can still control tag names, and even use HTML5y tags) and markup detachment (you don’t have to worry about syntax, and if you mess it up, it shows up right away on an error page), but you already know it, if you know HTML.

Posted via email from Bent Paperclips

Free Lego


Sorry, but it still kicks a fair amount of ass.

Via http://drbl.in/blfD & http://drbl.in/bliN

Posted via email from Bent Paperclips

1000 FPS Superbike Cornering

Running GoogleAppEngineLauncher on Port 80, Easily

So, you want to run the GoogleAppEngineLauncher on port 80 so you can—I don’t no—use your hosts file to record a screencast without having to hack in the proper URL somehow, even though the features you want to show off aren’t live yet? Also you’re using OS X.

Well everyone will tell you that port 80 is protected or requires root access, but what I haven’t seen anyone else say is that you can get around this pretty quickly.

First add your URL to the etc/hosts file, and direct it at your local IP (

Then, in terminal make a folder for the new prefs to live in (so you don’t have to keep creating the project over and over):

$ sudo mkdir -p /var/root/Library/Application\ Support/GoogleAppEngineLauncher $ sudo chmod 775 /var/root/Library/Application\ Support/GoogleAppEngineLauncher

Finally just launch the GoogleAppEngineLauncher from terminal as a sudoer:

$ sudo /Applications/GoogleAppEngineLauncher.app/Contents/MacOS/GoogleAppEngineLauncher

Add your project (don’t forget to set the port to 80), launch it and you should be ready to go.

Posted via email from Bent Paperclips

Designers are from Mars, and women re responsible for buying everything