How Technology Keeps Failing Us

and why we keep
repeating our mistakes

A look at the sidelines of history, to many of the research projects and products that promised to change how we use technology, but ultimately failed to make a big change in our everyday lives. Nostalgy for the lost opportunities, reminiscing about the promised futures, and an insistent hope that one day some of these things will come true, in one form or another. Hopefully these old new ideas will spur new innovation in you.

The topics covered will mostly be in the realm of computers and electronic gadgets, as that is what I've fiddled with.

Talk at BIL 2009-02-08, 15 min.

Sidelines of history

Good ideas
that never made it big
but should have
(I think so!)

15 minutes isn't that long, so I'm going to concentrate on one particular area where we see some struggling attempts to solve the problems, but where I would like to see a lot more emergence of functionality, something greater than the individual features.

15 min time

  • talking about just one scenario
  • grab me in the hallways to talk more

Plan 9 from Bell Labs

Glenda, the Plan 9 mascot bunny
  • Unix rethought
  • everything is a file(system)
  • seamlessly distributed
  • "infinite" storage

WORM

  • Write Once, Read Many
  • optical storage, before CD-Rs
  • hard drive was cache, written to WORM every night

Venti+Fossil

  • same idea, just hard drives
  • old versions of /my/file are at /snapshot/yyyy/mmdd/hhmm/my/file
  • don't bother with backups
  • eternal: growth was slow enough

Thin clients

  • move apps to server; no desktop IT
  • maybe force standard desktop

Sun Ray

The Sun Ray thin client hardware
  • "stateless desktop"
  • your keycard on any workstation
  • anytime, anywhere
  • easy, convenient, fast
  • everything exactly like you left it

http://en.wikipedia.org/wiki/Sun_Ray

On-Demand OS Image

  • NFS root
  • Live CDs (also VM, rootz)
  • OS Circular: full network boot

StatelessLinux: http://fedoraproject.org/wiki/StatelessLinux

  • read-only root filesystem over the network

rootz: http://vamosproject.org/rootz

  • "no install software", a read-only image fetched over HTTP and loop-mounted, with writable tmpfs union

OS Circular: http://openlab.jp/oscircular/

  • project to run virtual machines backed by SHA-verified blocks fetched over HTTP

Offline use

  • move apps & data onto laptop for travel
  • Coda allowed offline use of network filesystem
  • block-level migration for non-shared storage

Coda: http://www.coda.cs.cmu.edu/

Offline use

  • virtual machines can do live migration
  • Android makes apps seem "always on"
  • migrate virtual machine from server to laptop, leave snapshot on server in case laptop gets lost

Also interesting: http://en.wikipedia.org/wiki/Crash-only_software


What all that gets us

  • apps can migrate to faster CPUs
  • backups for everything
  • you can use any computer you choose to trust

What went wrong?

  • throw-away research projects
  • people believing in Imaginary Property; greed
  • short organizational memory
  • too much productization, too little standardization
  • NIH

Thank You

Slides are at eagain.net

Image credits: