| 5th | 10th | 15th | 20th | 25th | 30th | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 12am | ||||||||||||||||||||||||||||||
| 4am | ||||||||||||||||||||||||||||||
| 8am | ||||||||||||||||||||||||||||||
| 12pm | ||||||||||||||||||||||||||||||
| 4pm | ||||||||||||||||||||||||||||||
| 8pm |
A history lesson from Vint Cerf. I can’t help but picture him as The Architect in The Matrix Reloaded.
When Tim Berners-Lee invented and released the World Wide Web (WWW) design in late 1991, he found an open and receptive internet in operation onto which the WWW could be placed. The WWW design, like the design of the internet, was very open and encouraged a growing cadre of self-taught webmasters to develop content and applications.
Mark writes about his work with CERN to help restore the first website to its original URL.
I have two young children and I want them to experience the early web and understand how it came to be. To understand that the early web wasn’t that rudimentary but incredibly advanced in many ways.
It was twenty years ago today:
On 30 April 1993 CERN published a statement that made World Wide Web technology available on a royalty free basis, allowing the web to flourish.
A long-zoom data visualisation.
Some thoughts (and code) on responsive images.
Just as every instance of “the cloud” can be replaced with “the moon” or “my butt”, so too can every instance of the word “markets” in business reporting be replaced with the word “dragons”.
James has got you covered with this bookmarklet to do just that.
The dragons reacted strongly to the news.
A design fiction video depicting technology that helps and hinders in equal measure.
The accidental beauty in Google’s autosuggest algorithm.
A beautiful short film on the amazing work being done at the Internet Archive, produced on the occasion of their 10 petabyte celebration.
Truly awe-inspiring.
These are mostly just mean …but kinda funny.
Job postings that only use male pronouns.
See, this is why using “they”, while technically incorrect, can often be the least worst option.
A profile in The Guardian of the Internet Archive and my hero, Brewster Kahle (who also pops up in the comments).
A cute little read-only Twitter client from James that only displays fully-formed tweets: no hashtags, no @-replies.
A handy plugin for Chrome that always you to inspect media query breakpoints and take screenshots at any of them.
If, like me, you’ve been using the “export to SVG” plugin for Fireworks and then opening up the resultant file to trim it down, Josh has got you covered: here’s a version of “export to SVG” that will result in much slimmer files.
A beautiful piece by James on the history of light as a material for communication …and its political overtones in today’s world.
What is light when it is information rather than illumination? What is it when it is not perceived by the human eye? Deep beneath the streets and oceans, what is illuminated by the machines, and how are we changed by this illumination?
A terrific piece by Remy—based on a talk he gave—on when he uses jQuery and, more importantly, when he doesn’t. His experiences and conclusions pretty much mirror my own, but of course Remy is far more thoughtful and smart than I.
Really good stuff.
Heartbreaking and angry-making.
I concur with Ryan’s findings:
The best way to get better at what you do is to teach others how to do it, too.
These seem just about as reasonable as any other CAPTCHA.
The news is finally public: Bobbie’s Matter has been bought my Ev’s Medium. Fingers crossed that they don’t fuck it up.
Want to style those new HTML5 input types? I hope you like vendor prefixes.
A lovely description by Paul Ford of the Hypertext Transfer Protocol.
That simple handshake is the firmament upon which we have built trillion-dollar cathedrals and bazaars, the base upon which we construct other protocols and networks.
A lovely piece of writing from Richard on the nature of the web.
A couple of years ago, the benefits of separate sites were more clear to me. Today, I can’t think of a good reason to maintain a separate mobile site.
Jon gives some insight into how and why we use pattern portfolios as deliverables at Clearleft.
Trent hammers home the point that the kind of compartmentalisation that’s traditionally been part and parcel of the web dev workflow just won’t cut it anymore.
Keep it under your hat, but Paul has soft-launch his Project Portillo. And very nice it is too.
This looks like a handy little bit of JavaScript for progressively enhancing navigation lists to show/hide them on smaller screens. And it’s not a jQuery plug-in!
A good history lesson in rendering engines: KHTML, WebKit, and now, Blink.
Yes, yes, yes!
This is wonderful stuff! I’m a big fan of the datalist element but I hadn’t realised how it could be combined with input types like range and date.
So nifty!
These are like chindogu, but they’re all available from Amazon with accompanying reviews.
Dave talks about the kind of deliverables that get handed over in a responsive project. Sounds a lot like what we do at Clearleft.
Responsive deliverables should look a lot like fully-functioning Twitter Bootstrap-style systems custom tailored for your clients’ needs.
Some cautionary tales of over-engineering solutions before doing some quick user-testing to establish what the real problems are.
It’s a pleasant delusion to believe that all our problems require hard solutions.
A terrific, in-depth round-up and recollection of the Responsive Day Out by Laura that ties all of the strands together.
The story of one site’s disgraceful handling of acquisition and shutdown (Punchfork, acquired by Pinterest) and how its owner actively tried to block efforts to preserve user’s data.