“If it’s not curlable, it’s not on the web.” 📷 @jkphl
js;dr in print! Thanks to Joschi for the photograph of page 88 of @heydonworks’s new book “Inclusive Design Patterns”.
This book will last longer than all your fashionable JS frameworks no matter what your coding schools are teaching you. Except maybe jQuery. You can still use jQuery to build reliable web sites.
When I showed this photo yesterday to @adactio, he noted that the quote from my js;dr post:
“If it’s not curlable, it’s not on the web.”
sounded like something @benward had said in one of his blog posts from long ago. So we both researched it last night and found this post of Ben’s from 2011-02-11 “Hash, Bang, Wallop” https://benward.uk/blog/tumblr-3231388630
In which he notes:
“(It turns out that it was me who wrote “if site content doesn’t load through curl it’s broken”, and I'll stand by that.)”
Where the phrase “who wrote” links to:
Unfortunately that link now 404s. I assumed it was due to Yahoo shutting down all of YDN and so found this archive.org version instead (as noted tantek.com/2016/311/t1/site-content-load-through-curl)
While writing this post, and about to claim that YDN shut down (it did not), I double checked and remnants remained (top level blog URL etc).
There was no archive navigation (I’m not one to talk, I still need to build that on my site, maybe today at IndieWebCamp LA), so I paged through the "Previous" pages of the blog (eventually hacking the URL directly) and found:
Looks like YDN changed their CMS and broke all their permalinks.
This is pretty clear even from their own blog, e.g. the follow-up post to that post:
Which itself still links to the old permalink of the post it is following-up to.
In addition to breaking all their permalinks, they also removed all their comments, including Ben Ward’s comment, so we still have to go back to the archive.org link:
With Ben’s comment, which I’m going to quote in full because it provides a lot of the thinking behind js;dr before I wrote it up, and I figure providing yet another copy will help it stick around:
@BenWard on 2011-10-13:
“Of course, all of this is elaborate: The truth is that if site content doesn’t load through curl it’s broken.”
In particular, Ben’s point about:
This is really the key behind js;dr.
We still have this problem, six years later.
I *just* experienced this, this morning due to bad hotel wifi while trying to write this up! (as noted tantek.com/2016/311/t2/js-dr-pages-not-rendering-bad-hotel-wifi)
Networks are still slow or unreliable, no matter what device you may be using (like a laptop), no matter what country you may be in (here in the US, or in Europe, or elsewhere).
Lessons: make sure your sites and pages:
1. Show content immediately without waiting for ANY external JS.
2. Have meaningful readable text alternatives for all non-decorative images and other embedded content.
Previously, previously, previously: