Subscribe: stumblelog
Added By: Feedage Forager Feedage Grade C rated
Language: English
based  browser  css  diversity  mobile  opera  people  prefixes  speakers  twitter  users  vendor prefixes  vendor  web  webkit 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: stumblelog


written by Ben Darlow, a web developer in London, UK


Paths of Indiana Jones & Star Wars

Wed, 09 Jan 2013 18:56:07 +0000


Paths of Indiana Jones & Star Wars

You keep using that word…

Tue, 08 Jan 2013 20:24:16 +0000

I can see this thing is just going to run and run… Earlier today, following on from numerous others, Aral Balkan wrote about it: A person who calls for greater diversity is not necessarily advocating the implementation of a quota system — that’s a straw man fallacy No; it’s not. Diversity and merit‐based selection process are not mutually exclusive … No, but artificial diversity is mutually exclusive with meritocracy. Aral quotes Matt Andrews: I would have stopped once we’d reached, say, 17 male out of 22 possible speakers … that is to say, the last 5 speakers would be chosen based not on their merits but based on their gender, or artificial diversity. Aral continues: In an industry where 27–29% are female… Which industry is this again? The conference in question is for ‘[web] developers and browser vendors’; a field where the most recent A List Apart survey found approximately 9.1% of respondents who identified as such were women. … if you manage to get a speaker line‐up with 0% female speakers, you have a bias. Not necessarily; based on the above figures and assuming speakers were chosen purely on their strengths, you’d expect this to happen about 9% of the time for this number of speakers. People who are interested in seeing greater diversity at conferences are not calling for a quota system. That’s a straw man fallacy. … except for Matt Andrews whose suggestion is to stop selecting based on merit and start prioritising by gender at an arbitrary number. In other words: a quota. It’s not a straw man: it’s an accurate description of what it is. If, however, you reach 17 speakers and they’re all male, you should realise that you’ve reached a point where you need to take a moment to introspect your process and attempt to modify it to reduce your selection bias. This does not mean that you stop at 17 and start looking for five women as Matt states. It means that you go back to step one and re‐evaluate your entire selection process. ‘In order to solve the diversity issue first one must re-invent the universe’. We’ll come back to this one. The Diversity versus Meritocracy False Dichotomy. This fallacy […] erroneously implies that diversity and meritocracy are somehow mutually exclusive Now who’s using straw men arguments? Nobody, I think, would argue that it’s impossible to have both a diverse and merit-based collection of conference speakers. What is being argued is that artificial diversity is mutually exclusive with using merit as the sole deciding factor. As has been shown, you simply can’t guarantee that a set of speakers can always be gender-diverse given how few women work in web development. Aral then posits an alleged argument put forward: The conference has an all‐male speaker list, therefore the selection process must have been a meritocracy I’m interested in hearing who thinks this, other than bigots from Hacker News. I’ve not seen a single rational argument on this subject which boils down this way. Another version of this argument goes: A conference that has a meritocratic selection process is bound to end up with few women. Again, this is confusing correlation with causation. It is doing nothing of the sort; the number of female web developers in the industry has a direct impact on the number of potential speakers for a conference that are female. Period. Not acknowledging this is essentially sticking your head in the sand. Let’s rephrase it: A conference with a merit-based selection process is statistically more likely to result in fewer speakers from statistical minorities. If you still refute this, then I have some ‘lucky’ lottery numbers to sell you. As the three conferences linked to above can testify, not only is diversity possible in a meritocracy, it can actually thrive in one. Again, nobody is saying diversity can’t happen. But you shouldn’t kid yourself that a statistical minority beating the odds of representation [...]


Wed, 19 Sep 2012 22:00:51 +0100



Tue, 18 Sep 2012 22:54:04 +0100

width="400" height="225" id="youtube_iframe" src="" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>

This Is For Everyone

Thu, 02 Aug 2012 21:58:53 +0100

But then all of a sudden the Olympic opening ceremony comes along, and millions of people sense - instinctively - that it isn’t either-or or us-and-them. You can like and respect and respond to both Elgar and Dizzee, both the romantic national myth of the countryside and the achievements of the Industrial Revolution, both the older traditions cherished by the Right and the post-war developments cherished by the Left. On Friday night, miraculously, it suddenly all seemed to be part of one narrative, part of a shared national story.

Robin Carmody absolutely nails it — this is exactly why the ceremony brought a lump to my throat; the realisation that yes; this country of mine is unique and special and worth celebrating!

Why I'm backing

Fri, 20 Jul 2012 12:37:00 +0100

Like many long-time Twitter users, I’m deeply concerned by the imminent (but as yet unconfirmed) threat to third-party developers who make use of the Twitter API. Twitter has evolved a great deal since its inception, but it would be wrong not to give credit to the ingenuity of third-parties who have helped make the service what it is today. Just to give a few examples: The term ‘tweet’ was coined by users, not the company themselves; it’s now the official term for an update posted to the site. Hashtags, retweets, @replies and embedded media: all conceived by users and third-parties before being subsumed into the official Twitter product. The iPhone’s arrival led to the creation of numerous innovative clients, whose behaviour inspired and directed the evolution of the web client, as well as in one case being acquired by Twitter as the first official iOS client. Even Twitter’s branding is essentially a riff on the Twitterriffic Bird; the iconic design by David Lanham was clearly the inspiration for the bird which now serves as Twitter’s only brand mark. The rationale for Twitter’s presumed cutting off third-parties is ostensibly about delivering a consistent experience, but the unspoken motive is financial: to ensure that advertising can’t be bypassed by a third-party client. But there is a problem here, predicated on an assertion Michael Wolff makes in his fascinating article ‘The Facebook Fallacy’; that advertisers are seeing reduced returns on their investment, with the net result that the value of online advertising is decreasing. To an extent, technological innovation and clever targeting can offset some of that decrease, but the endgame should be clear to all: that either the same amount of advertising will yield less revenue, or the amount of advertising will have to increase. The outcome of this battle is beginning to sound increasingly user-hostile. I believe Twitter is one of the most important social inventions of the 21st century, and has tremendous power. That moment of realisation came for me first when Flight 1549 crash-landed in New York’s Hudson River, and was photographed by an iPhone user, shared via TwitPic. That photo was seen all around the world within hours, but wasn’t on the front page of newspapers until the following day. I later saw how it could be commercially invaluable when I was contacted directly by Etymotic Research after mentioning on Twitter that my earphones had broken, and they offered to replace them. All around the world companies now employ ‘social media’ staff, whose role is now effectively proactive customer service. This usefulness is at risk if Twitter transforms into a vehicle for focused advertising, and I don’t want to see that happen. I’d rather see Twitter die and something else take its place, in fact. Luckily it seems I’m not the only one who feels strongly about this, and so I’m happy to contribute towards an effort to build something that can serve the same (if not a better) purpose, that won’t be beholden to advertisers. And if you are remotely as passionate about this as I am, then I urge you to pledge to contribute too.[...]

"How has it been possible for banks to grow from less than 4 per cent of the global economy to more..."

Wed, 11 Jul 2012 14:34:35 +0100

How has it been possible for banks to grow from less than 4 per cent of the global economy to more than 12 per cent of the global economy without impoverishing others? How has it been possible for profits in the financial sector to be consistently higher than profits from other human endeavors with more tangible products or impacts on our daily lives - such as agriculture, transport, health care or utilities? How has it been possible that banks derive their profits not from the protected and regulated activities of deposit-taking and lending, but from the unsupervised and often unknowable escalation of off-balance sheet assets and liabilities? How has it been possible that pension savings have increased while pension returns have declined to the point where only bankers can expect a comfortable old age?

Global banks have built the casinos and tilted the odds in the house’s favour by rigging the data that determines the outcomes of most of the bets on the table. Every one of us that sits at the table long enough - whether saver, investor, borrower, taxpayer or pensioner - will be a loser. It is not a flaw; it is feature.

- Lies, Damn Lies and LIBOR.

Mail is now using 4.61 GB of RAM

Tue, 03 Jul 2012 12:02:28 +0100

Mail is now using 4.61 GB of RAM
well, have you ever put any thought into how much memory it takes to store retina-quality text?
that display is approximately 8 times crisper than a regular non-retina display
and each pixel is actually a portrait of steve jobs
actually no
cause then those would be dead pixels

On Opera & Vendor Prefixes

Mon, 30 Apr 2012 21:32:53 +0100

Reacting to Opera’s announcement that their latest experimental builds of their browser software would be spoofing certain -webkit vendor prefixes, I somewhat antagonistically vented on Twitter: Hey Opera: nobody uses your crappy browser. Thanks for dicking over the web by implementing -webkit prefixes anyway. Okay, the first part is most certainly not true; a lot of people use Opera (and as it happens, they have just published their State of the Mobile Web report for March 2012, so we can see what the data looks like right now). But whilst what I wrote was undoubtedly confrontational, having now looked some more into the situation I’m convinced that Opera have made a terrible decision out of desperation that will permanently damage web standards for little gain. Opera is actively involved in the development of two mobile-oriented browsers: the enormously popular but atypical Opera Mini which mostly runs on older and non-smartphone devices, and the more modern smartphone-oriented Opera Mobile. When I asked, I was told that separate figures for how many people use each browser are unavailable. Given how eager Opera are to boast about how many Opera Mini users they have, it’s pretty easy to conclude that the number of Opera Mobile users is a lot smaller. This is significant, as a major justification given for spoofing vendor prefixes is that it affects a lot of people; Opera currently only intend to make the change within Opera Desktop and Mobile. Opera have tried to throw a feint by insinuating that this is to prevent their users from being locked out: When people block access by certain browsers, whether by omitting CSS rules or actively blocking, we have a duty to our users to access that content. This is an egregious straw man: the prefixes Opera are implementing are limited to transitions, transforms, border radius and box shadows. None of these are barriers to being able to access content; this is just how progressive enhancement works. As it stands today, Opera Software is a profitable and growing business, as their latest quarterly report attests (PDF link). But this masks the underlying sea change that’s happening with mobile Internet-enabled devices. Opera (along with Mozilla and Microsoft, the other parties intending to make this vendor prefix change) know full well that they’re sitting on sand castles as the tide comes in. An increasingly large number of the mobile phone devices sold today are either iOS or Android-based, and as the technology matures and economies of scale improve, the share of the market that once belonged to feature phones will be swallowed up by cheaper iOS or Android devices. Experienced web developers know that encouraging customers to install another browser is a difficult if not impossible task. It’s even less likely that smartphone users will feel any need to install a third-party browser on their device when the default browser is easily good enough to begin with. Opera are faced with the knowledge that within a few short years, their user base could be eroded to almost nothing. This move is reflective of this realisation, and is one made out of desperation, with little concern for the long term implications to web developers and the standards process. Vendor prefixes are, to be sure, a mess. But the situation we find ourselves in is not the fault of vendors implementing features this way, but of the glacial pace of the CSS Working Group in ratifying features that are already in widespread use. That another browser vendor feels able to spoof them shows the feature is already mature. The danger now is that ‘bad’ web developers will treat -webkit as more than just a de facto standard, and the march towards a single dominant browser in the mobile space will gather pace.[...]


Thu, 08 Mar 2012 21:50:38 +0000


Some advice for the Mozilla Corporation

Thu, 16 Feb 2012 11:50:22 +0000

Forget vendor prefixes; that’s like trying to apply the leeches; you’re doing the patient harm, and it’s not going to cure the problem. There will always be a web. So, if you want your software to remain relevant in the post-PC economy, your software needs to be on the devices that people use to browse the web. And if you are really serious about software, you should make your own hardware.

The W3C's WebKit Problem

Thu, 09 Feb 2012 10:13:00 +0000

Once again we’re at a crossroads with the Open Web, with the not-so-hollow threat from browser makers that are not Apple or Google to implement the -webkit prefix for CSS extensions. WebKit has long led the field for CSS extensions, implementing features such as text-shadow as far back as 2003, but the browser landscape has radically altered since the introduction of the iPhone. CSS features once considered idealistic have rapidly become a standard part of the web developer toolkit. The transformative effects of this new era of mobile computing are still being felt, and we’ve yet to see just how the dust will settle, with major players such as Nokia and Microsoft yet to find their footing. What is for certain though is that they won’t give up without a fight. I find it shocking that this incredibly strong business driver has yet to be recognised as the rationale behind this threat. Microsoft, Mozilla and Opera have all yet to properly assert themselves in the new mobile web economy, and all three are at massive risk of being left behind. The fact that Opera is a major player on a massive number of existing devices is next to irrelevant when you consider just how quickly phones are replaced in comparison to desktop computers. Mozilla also faces strong competition; for years the darling of open web advocates, Firefox has long had a reputation for being a slow, memory hog, but recently many in the technology community are finally switching to Chrome. When your previously biggest advocates are turning their back on you, it doesn’t bode well for how the more fickle majority will act. Then there’s Microsoft. As I wrote two years ago, Microsoft needed to embrace the open web or risk irrelevance. To my surprise (but a pleasant surprise), this is exactly what they’ve done, and with Windows 8 they’re forging a path away from Silverlight and towards a new era of apps built for touch devices upon open web technologies. But it’s quite possible this is too little, too late. The iPad is utterly crushing the competition in the tablet market, and by the time Windows 8 is in the hands of consumers on a tablet device, the marketplace may have already decided that all they want is iPads. In turn, developers will be basing their technology decisions upon this. Finding no alternative, they will turn to the -webkit CSS extension wherever they want to make use of modern CSS features. Which brings us back to the W3C. That there is no other choice but to use vendor prefixes in spite of the fact these target mature and reliable technologies is a massive indictment of the W3C’s CSS working group. These should be features by now. If there is still debate over syntax, that the development community uses them anyway should be a big pointer as to whether or not that’s an important debate (and before you assume this means that the -webkit syntax will always win, there are numerous examples of syntaxes that WebKit introduced that have been superceded; -webkit-gradient immediately springs to mind). Pointing the finger at the people who build websites when they have no reasonable alternative (other than to just not use the features!) is the worst kind of passing the buck, but when the remit of a working group is to be apolitical it’s too easy not to recognise when you’re being gamed. And that’s precisely what’s happening right now. So, what needs to happen? Do authors need to change? Well, browser sniffing was always bad; good developers have known this for over a decade, and so a call to action on this is preaching to the crowd. Using all available vendor prefixes for a given feature is naturally better than only -webkit, but there are certain situations when it’s not[...]

Spinner animation using CSS3 transitions

Mon, 06 Feb 2012 11:03:00 +0000

style="width: 100%; height: 300px" src="" allowfullscreen="allowfullscreen" frameborder="0">

For those browsers that now support it (read: recent Firefox versions, Safari 5 and iOS 5 Mobile Safari) you can now use steps(x,y) as your transition-timing-function, permitting the creation of sprite frame-based animations. This example doesn’t even need that, as it just rotates the same image by 30° each frame.

Serve a static website on an arbitrary local domain under Mac OS with Pow

Wed, 25 Jan 2012 16:43:40 +0000

curl | sh ; mkdir ~/Sites/foo ; mkdir ~/Sites/foo/public ; echo '

hello world

' > ~/Sites/foo/public/index.html ; ln -s ~/Sites/foo ~/.pow/foo ; curl

No need for a, just symlink it and you’re away.


Sun, 27 Nov 2011 10:25:35 +0000

src="" width="400" height="225" frameborder="0" title="Address Is Approximate" webkitallowfullscreen mozallowfullscreen allowfullscreen>


Sun, 27 Nov 2011 10:22:01 +0000


Thu, 06 Oct 2011 08:00:39 +0100

Without Apple, I quite simply wouldn’t be the person I am today. I grew up with computers, but I only used them to play games (and very occasionally write letters) until I used a Mac. It was on a Mac I was first inspired to be creative and build things using computers. I designed magazine pages. I drew icons. I wrote my first software program on a Mac, and set in motion the wheels of my future career, and it was on a Mac I designed and built my first website.

Steve Jobs has died, but his vision and drive live on through millions of people like myself, who were captivated and inspired by the products that he and the many other brilliant people at Apple created. The world is a richer, better place for him having been in it. Whilst our first thoughts whenever we lose somebody may be of how much emptier life suddenly feels without them, the impact they’ve had on us all is still with us, and always will be.

Thank you, Steve.


Tue, 30 Aug 2011 14:15:19 +0100



Fri, 12 Aug 2011 07:58:50 +0100



Tue, 09 Aug 2011 22:36:05 +0100