We were struggling, whether we knew it or not, to found a more fluid society. A place where everyone, not just appointed apologists for the status quo, could be heard. That dream need not die. It matters more now than ever.
December 12th, 2013
December 9th, 2013
Alas, it turns out that it’s reliant on user-agent string sniffing. I guess that’s to be expected: this isn’t something that can be detected directly. Still, it feels a little fragile: whenever you use any user-agent sniffing tool you are entering an arms race that requires you to keep your code constantly updated.
Another good ol’ rant from Tom. It’s a bit extreme but the underlying lamentation with the abandonment of progressive enhancement is well founded.
Some good brainstorming from Tantek that follows on nicely from Anne’s recent manifesto.
A blog covering the conservative dinosaur readiness movement.
December 8th, 2013
Ant—the latest super-smart addition to the Clearleft team—describes this year’s Hackfarm, which happened a couple of weeks ago.
It was Ant’s first week. Or, as he described it when we were wrapping up all the hacking, “Best first week at a job ever!”
Here’s a heartwarming tale. It starts out as a description of processing.js project for Code Club (which is already a great story) and then morphs into a description of how anyone can contribute to make a codebase better …resulting in a lovely pull request on Github.
December 6th, 2013
Some excellent research from Chris, canvassing opinions on whether there’s a difference between web “apps” and web “sites”. His conclusion:
Almost none of the points above ring true for me. All I see are exceptions and gray area.
If nothing else, the fact that none of the proposed distinctions agree with one another show how pointless the phrase “web app” is—if people have completely differing ideas on what a phrase means, it is completely useless in furthering discussion …the very definition of a buzzword.
This leads me to think perhaps the “web app” moniker (certainly the newer of the two) is simply just a fashionable term. We like the sound of it, so we use it, regardless if it truly means anything.
But all of this is, I think, missing the more important point: why? Why would you want to separate the cornucopia of the web into two simplistic buckets? What purpose does it serve? That’s the question that really needs be answered.
If we could pin down a super accurate definition that we agreed on, even then it might not be particularly useful. And since we can’t, I argue it’s even less useful.
December 5th, 2013
Chloe is going all in on the Indie Web. Here, she outlines how she’s posting to Twitter from her own site with a POSSE system (Post to Own Site, Syndicate Elsewhere).
December 3rd, 2013
This is a wonderful, wonderful round-up by KQED of the most recent Science Hack Day in San Francisco …a truly marvellous event.
Be sure to watch the accompanying video—it brought a tear to my eye.
A superb bit of sleuthing by James:
From London to the Mediterranean, to Malta and back again, over multiple countries and jurisdictions, through airspace and legal space. The contortions of G-WIRG’s flight path mirror the ethical labyrinth the British Government finds itself in when, against all better judgements, it insists on punishing individuals as an example to others, using every weasel justification in its well-funded legal war chest. Using a combination of dirty laws and private technologies to transform and transmit people from one jurisidiction, one legal condition and category, to another: this is the meaning of the verb “to render”.
John shares his concerns about the increasing complexity involved in developing for the web.
Coming from anyone else, this glorious vision might seem far-fetched, but Anne is working to make it a reality.
December 2nd, 2013
The transcript of Mark’s talk from last week’s Handheld conference in Cardiff.
There are mountains.
December 1st, 2013
This was my favourite moment from the Handheld conference in Cardiff.
November 30th, 2013
Some excellent practical advice on progressive enhancement.
I agree completely with the sentiment of this article (although the title is perhaps a bit overblown): you shouldn’t need a separate API—that’s what you’re existing URL structure should be.
I’m not entirely sure that content negotiation is the best way to go when it comes to serving up different representations: there’s a real value in being able to paste a URL into a browser window to get back a JSON or XML representation of a resource.
But this is spot-on about the ludicrous over-engineered complexity of most APIs. It’s ridiculous that I can enter a URL into a browser window to get an HTML representation of my latest tweets, but I have to sign up for an API key and jump through OAuth hoops, and agree to display the results in a specific way if I want to get a JSON representation of the same content. Ludicrous!
November 29th, 2013
The closing keynote from the border:none event held in Nuremberg in October 2013.
November 26th, 2013
Usually I find these kinds of name-and-shame collections to be unnecessarily mean-spirited. In this case, the sites being named and shamed are themselves guilty of far worse rudeness.