The width of our modern cars, Hummers notwithstanding, is descended from the width of Roman chariots. Now while this has been debated as coincidence by some, the fact remains that rutted roads would have been very awkward to drive on if your car had a signficant width difference. Some people go so far as to claim this development was by edict – but it’s much easier to understand the mechanics of the situation. These things were more than coincidence – they were common sense. They didn’t happen by edict, they happened because their developers had a challenge and had real world problems to deal with.
In Jaron Lanier’s “You Are Not A Gadget”, he treats us to another example. Victorian railroad tunnels were re-used for the modern London Underground system. Sadly the tunnels are sufficiently narrow that while they can accommodate the trains, they can’t accommodate an air-conditioning system without a serious amount of rework. Which means consumers end up with a hot and stuffy travel experience in one of the greatest cities in the world.
I’m told, but can’t find a reference, for the 20 kg (40 lb) weight limit on carry on items being due to stagecoach limits?
I see this in computing. In 1984, everyone thought that the Macintosh was a step too far. Computers had black and white (or green) interfaces. And twenty-six years later, we’re all using more or less the same interface. While it would be easy to blame the market leader for a lack of innovation (and even easier to point at them as a cause of stagnancy in the computing industry as a whole). We’ve not come a long way from 1984. We have files, we have a single mouse pointer. Yes, our computers are bigger, faster and more colourful but we still poke with a single finger at our files and and pictures. Our computers can do a lot more – but these things are tasks – we don’t see much of the operating system when we’re playing a game nor when we operate a word processor. The Operating System becomes simply a way to access these tasks and for the most part we only perform one task at a time. We don’t write a novel while we’re playing a game. We don’t tend to design elegant infographics while we’re also mixing a sequence of music to accompany that infographic. We do one thing at a time.
Where this breaks down is in the simple mechanics of tasks versus ‘apps’. I keep most of my music on my iPhone and play this while tapping out emails and tweets. However if I want to use a service like Spotify, then I have some problems. Spotify is an “app” on the iPhone and only one “app” can run at a time which means I can listen to music from Spotify or I can write email, but not both. For me, that’s not a pain but it is why I suggested ‘backgrounding‘. I’m not too worried about Spotify because I don’t use it – but I can see more of this in the future – where there is a need to hook into a service in the background and there will be a solution in place.
The resistance to task-based interfaces is perplexing though – especially from the crowd who lauded the appearance of Wizards – software designed to make certain tasks easier – not designed to help productivity itself but rather to overcome the increasing complexity of computer operating systems. So let’s envisage a product representing the next stage of computing, the removal of that complexity – not the obfuscation of complexity behind a Wizard, simply the removal of it.
What would that product look like?