Books and the Problem with their Future

The fall of old media and the maturing of new is a key aspect of network culture. Never before have the forms of media and the means by which they have been distributed and read changed so quickly.

But speaking as a historian, designer, and author (not to mention as media review editor of the Journal of the Society of Architectural Historians), I am concerned about the future of media. In particular, I worry about how the formats being developed in media are evolving.

Books and periodicals have proved robust over time. It's easy to pick up a book from the sixteenth century and read it. The publications of our day, on the other hand, are posing a problem to future readers.

On the one hand, we have PDFs. Nobody seems to like PDFs and their capabilities are rather limited. They are hard to protect and easy to disseminate, making publishers wary of them (the vast majority of book piracy is in PDF). PDFs maintain the format of the printed page, which is great when you need it, but also a limitation (for example, older readers can't make the text larger). eBooks such as found on the Kindle and on Apple's iBooks stores seem to have more robust digital rights management protection but can also be hacked and freely distributed (never underestimate the book pirates: they will win in the end just as they did with music). But these eBooks are even more limited than PDFs. Formatting is quite limited and adding rich media such videos as to the text hasn't proved possible yet. These eBooks are, if anything, a step back from the PDF and even the book, becoming nothing less than some kind of weird intermediary between the scroll and the codex. 

Then there are app books for the iPad, Android, and other tablet computers, such as Wolfram's the Elements or Phaidon's Design Classics. As librarian John Dupuis points out on his blog, these are visually compellling but an outright disaster for users in the long run. The model of book ownership that prevailed for so many years is now replaced by a model of licensing. Yes, it appears that you purchased Design Classics, but can you resell it? Can you give it to a friend for a birthday present? Can you take the pages in it and cut them up for an art project? Can you check it out from a library? Will you be able to take it with you if you tire of your iPad and want to move to an Android? Generally speaking, all of these are impossible.  

As Dupuis suggests, some kind of open access and standards based authoring environment needs to be developed for the book world. How long will this take to emerge? When I first saw Apple's Hypercard authoring environment in 1987, I was certain that the future of the book had arrived. But now, that future has gone into the past, almost irretrievably so (go ahead, just try to open a Hypercard stack from 1987 such as the incredible Zaum Gadget).   

Nor is the Web immune to these problems. HTML is limited so Web owners turn to authoring environments like Flash or content management systems like Drupal, (which serves this site). But if I stop updating this site, even if I continue to pay the bills for the hosting and the domain name servers, one day the PHP programming language or the MySQL database on which Drupal run will be updated to the point that an update to Drupal will be required. Drupal has this mantra called "the drop keeps moving" which basically means any module or extension involved in this site (and there are many) as well as the theme (or graphic layout) will break unless it is updated too. Even if someone was able to log into my site and update it, they would have to update the modules and the theme. Now, I am sure my readership would rather that I write more and update the architecture to my site less (unless that update is necessary for functionality) so I try to update as little as possible but when I do a major update, I generally devote two to three weeks to update all of my sites (audc.org, networkarchitecturelab.org, docomomo-us.org, networkedpublics.org and so on). Now I could export everything to HTML and forget about updating the site ever again. That could last a long time (for example, my friend Derek Gross died in 1996 but his site is still up) but that conversion process too is likely to take at least a week and would require a Drupal developer. Is that going to happen? Probably not.

None of this is new. The Institute for the Future of the Book has been talking about this for years now. But this is a crisis of major proportions for anyone involved in thinking about human culture in the long term and we need to make all the noise about it we can.  

The fall of old media and the maturing of new is a key aspect of network culture. Never before have the forms of media and the means by which they have been distributed and read changed so quickly.

But speaking as a historian, designer, and author (not to mention as media review editor of the Journal of the Society of Architectural Historians), I am concerned about the future of media. In particular, I worry about how the formats being developed in media are evolving.

Books and periodicals have proved robust over time. It's easy to pick up a book from the sixteenth century and read it. The publications of our day, on the other hand, are posing a problem to future readers.

On the one hand, we have PDFs. Nobody seems to like PDFs and their capabilities are rather limited. They are hard to protect and easy to disseminate, making publishers wary of them (the vast majority of book piracy is in PDF). PDFs maintain the format of the printed page, which is great when you need it, but also a limitation (for example, older readers can't make the text larger). eBooks such as found on the Kindle and on Apple's iBooks stores seem to have more robust digital rights management protection but can also be hacked and freely distributed (never underestimate the book pirates: they will win in the end just as they did with music). But these eBooks are even more limited than PDFs. Formatting is quite limited and adding rich media such videos as to the text hasn't proved possible yet. These eBooks are, if anything, a step back from the PDF and even the book, becoming nothing less than some kind of weird intermediary between the scroll and the codex. 

Then there are app books for the iPad, Android, and other tablet computers, such as Wolfram's the Elements or Phaidon's Design Classics. As librarian John Dupuis points out on his blog, these are visually compellling but an outright disaster for users in the long run. The model of book ownership that prevailed for so many years is now replaced by a model of licensing. Yes, it appears that you purchased Design Classics, but can you resell it? Can you give it to a friend for a birthday present? Can you take the pages in it and cut them up for an art project? Can you check it out from a library? Will you be able to take it with you if you tire of your iPad and want to move to an Android? Generally speaking, all of these are impossible.  

As Dupuis suggests, some kind of open access and standards based authoring environment needs to be developed for the book world. How long will this take to emerge? When I first saw Apple's Hypercard authoring environment in 1987, I was certain that the future of the book had arrived. But now, that future has gone into the past, almost irretrievably so (go ahead, just try to open a Hypercard stack from 1987 such as the incredible Zaum Gadget).   

Nor is the Web immune to these problems. HTML is limited so Web owners turn to authoring environments like Flash or content management systems like Drupal, (which serves this site). But if I stop updating this site, even if I continue to pay the bills for the hosting and the domain name servers, one day the PHP programming language or the MySQL database on which Drupal run will be updated to the point that an update to Drupal will be required. Drupal has this mantra called "the drop keeps moving" which basically means any module or extension involved in this site (and there are many) as well as the theme (or graphic layout) will break unless it is updated too. Even if someone was able to log into my site and update it, they would have to update the modules and the theme. Now, I am sure my readership would rather that I write more and update the architecture to my site less (unless that update is necessary for functionality) so I try to update as little as possible but when I do a major update, I generally devote two to three weeks to update all of my sites (audc.org, networkarchitecturelab.org, docomomo-us.org, networkedpublics.org and so on). Now I could export everything to HTML and forget about updating the site ever again. That could last a long time (for example, my friend Derek Gross died in 1996 but his site is still up) but that conversion process too is likely to take at least a week and would require a Drupal developer. Is that going to happen? Probably not.

None of this is new. The Institute for the Future of the Book has been talking about this for years now. But this is a crisis of major proportions for anyone involved in thinking about human culture in the long term and we need to make all the noise about it we can.  

Leave a Comment