tomorrow and tomorrow

The future has only been a topic of interest for a relatively short while.
For most of time the future was likely to be pretty much like the past except we’d be dead then and replaced by replica offspring – same job, same village, same stories. Utopia was in heaven not a century hence and the gods were our time lords. When exactly did we start to picture fantastical possibilities to come? I grew up in a generation where everyone looked to space travel and videophones around the corner with excitement and trepidation. Tomorrow’s World was a BBC TV show where bizarre prototype inventions were revealed and we prepared to live on capsule meals and drift around our (bookshelfless) spacepods in smooth lycra jump suits.

Now we don’t expect to wait for new gizmos. The Millennium celebration led to more futuregazing of the glibbest kind. Everywhere were teams of youngsters singing hymns to a harmonious, multicultural, tolerant tomorrow. Then 9/11. And in 2008 the whole planet is fretting as a new day suddenly dawns of rising food prices and sea levels. Tomorrow has come after all rather suddenly and it isn’t smiling.
In this context The Book of the Future sounds like some superheroic accoutrement, nostalgically space aged, something Batman keeps tucked down his utility belt, a magical entity that might just help to save the planet: a bleeping symbol of meaning and quality in a chaotic, cruel world.
O, all powerful Internet, come to my aid! I’m in need of further reading on the history of the future.
All suggestions welcome.

interface culture

Omnisio, a new Y Combinator startup, lets people grab clips from the Web and mash them up. Users can integrate video with slide presentations, and enable time-sensitive commenting in little popup bubbles layered on the video.
MediaCommons was founded partly to find a way of conducting media studies discussions at a pace more congruent with changes in the media landscape. It’s tempting to see this as part of that same narrative: crowdsourcing media commentary for the ADHD generation. For me, though, it evokes a question that Kate Pullinger raised during the research Chris and I conducted for the Arts Council. Namely: are we seeing an ineluctable decline of text on the Web? Are writers becoming multi-skilled media assemblers, masher-uppers, creators of Slideshares and videocasts and the rest? And if so, is this a bad thing?
I’ve been re-reading In The Beginning Was The Command Line, a 1999 meditation by Neal Stephenson on the paradigm shift from command line to GUI interactions in computer use. In a discussion on Disneyland, he draws a parallel between ‘Disneyfication’ and the shift from command line to GUI paradigm, and thence to an entire approach to culture:

Why are we rejecting explicit word-based interfaces, and embracing graphical or sensorial ones–a trend that accounts for the success of both Microsoft and Disney?
Part of it is simply that the world is very complicated now–much more complicated than the hunter-gatherer world that our brains evolved to cope with–and we simply can’t handle all of the details. We have to delegate. We have no choice but to trust some nameless artist at Disney or programmer at Apple or Microsoft to make a few choices for us, close off some options, and give us a conveniently packaged executive summary.
But more importantly, it comes out of the fact that, during this century, intellectualism failed, and everyone knows it. In places like Russia and Germany, the common people agreed to loosen their grip on traditional folkways, mores, and religion, and let the intellectuals run with the ball, and they screwed everything up and turned the century into an abbatoir. Those wordy intellectuals used to be merely tedious; now they seem kind of dangerous as well.
We Americans are the only ones who didn’t get creamed at some point during all of this. We are free and prosperous because we have inherited political and values systems fabricated by a particular set of eighteenth-century intellectuals who happened to get it right. But we have lost touch with those intellectuals, and with anything like intellectualism, even to the point of not reading books any more, though we are literate. We seem much more comfortable with propagating those values to future generations nonverbally, through a process of being steeped in media.

So this culture, steeped in media, emerges from intellectualism and arrives somewhere quite different. Stephenson goes on to discus the extent to which word processing programs complicate the assumed immutability of the written word, whether through system crashes, changing formats or other technical problems:

The ink stains the paper, the chisel cuts the stone, the stylus marks the clay, and something has irrevocably happened (my brother-in-law is a theologian who reads 3250-year-old cuneiform tablets–he can recognize the handwriting of particular scribes, and identify them by name). But word-processing software–particularly the sort that employs special, complex file formats–has the eldritch power to unwrite things. A small change in file formats, or a few twiddled bits, and months’ or years’ literary output can cease to exist.

For Stephenson, a skilled programmer as well as a writer, the solution is to dive into FLOSS tools, to become adept enough at the source code to escape reliance on GUIs. But what about those who do not? This is the deep anxiety that underpins the Flash-is-evil debate that pops up now and again in discussions of YouTube: when you can’t ‘View Source’ any more, how are you supposed to learn? Mashup applications like Microsoft’s Popfly give me the same nervous feeling of wielding tools that I don’t – and will never – understand.
And it’s central to the question confronting us, as the Web shifts steadily away from simple markup and largely textual interactions, toward multifaceted mashups and visual media that relegate the written word to a medium layered over the top – almost an afterthought. Stephenson is ambivalent about the pros and cons of ‘interface culture’: “perhaps the goal of all this is to make us feckless so we won’t nuke each other”, he says, but ten years on, deep in the War on Terror, it’s clear that hypermediation hasn’t erased the need for bombs so much as added webcams to their explosive noses so we can cheer along. And despite my own streak of techno-meritocracy (‘if they’ve voted it to the top then dammit, it’s the best’) I have to admit to wincing at the idea that intellectualism is so thoroughly a thing of the past.
This was meant to be a short post about how exciting it was to be able to blend video with commentary, and how promising this was for new kinds of literacy. But then I watched this anthology of Steve Ballmer videos, currently one of the most popular on the Omnisio site, and (once I stopped laughing) started thinking about the commentary over the top. What it’s for (mostly heckling), what it achieves, and how it relates to – say – the kind of skill that can produce an essay on the cultural ramifications of computer software paradigms. And it’s turned into a speculation about whether, as a writer, I’m on the verge of becoming obsolete, or at least in need of serious retraining. I don’t want this to lapse into the well-worn trope that conflates literacy with moral and civic value – but I’m unnerved by the notion of a fully post-literate world, and by the Flash applications and APIs that inhabit it.

a new blog format avoids the tyranny of chronology

Sebastian Mary and i were talking last week about the need to re-conceive the format of if:book so that interesting posts which initiate lively discussions don’t get pushed to the bottom. a few days later i met with Rene Daalder who showed me his new site, Space Collective which is a gorgeous and brilliant re-thinking of the blog. click on “new posts” and notice how you can view them by “Recently Active, Most Popular, Newest First, and Most Active.” Also notice the elegant way individual posts emerge from the pack when you click on one of them. Please, if you know of other sites which are exploring new directions for the blog, please put the URL into a comment on this post.

a return to orality

I’ve been making my way through Robert Bringhurst’s The Tree of Meaning: Language, Mind and Ecology, which came out a couple years ago in Canada, but which is now getting an American release from Counterpoint. Bringhurst is probably best known to the readers of this site as the author of The Elements of Typographic Style, though he’s well-known as a poet and translator of Native American languages in Canada. This book is a collection of essays looking broadly at oral, written, and visual language and culture through an ecological lens, a viewpoint not dissimilar to the gatherings of wood s lot, the work of his fellow Canadian Mark Woods.
Much of The Tree of Meaning looks at Native American literature of the Pacific Northwest and how that was gathered by the followers of Franz Boas who gathered and disseminated native stories in songs. I know painfully little about anthropology; perhaps that’s why Bringhurst’s words on the problems inherent in transcribing oral literature seem evocative:

It is true that writing changes literature. It changes it, first of all, by leaving things out. A transcript of an oral poem never captures the fullness of a living performance tradition. And this is where writers become more deviant still. As they take their own dictation, they begin to try to use the resources of writing to patch up the holes and mend the tears they cannot help but make in the fabric of literature as they slip from the oral tradition.

(p. 178 in “The Humanity of Speaking: The Place of the Individual in the Making of Oral Culture”.) The idea of the printed word as being what’s left behind isn’t one we commonly think about, but it instinctively makes sense – perhaps more than ever in a world where a book can be simmered down to a text file constrained to the 127 ASCII characters. Looking to return closer to the original poetry, Bringhurst investigates John R. Swanton‘s typographic transcriptions of Haida myth and finds that document to be more complex than we commonly give it credit for:

The typescript, like the photograph, filters and compresses features of reality. We have to learn to read it – and I don’t just mean we have to learn the language. Learning to read transcriptions of oral literatures is something like learning to read historical photographs. The depth and the color, the sounds and the smells, the coughing and spitting, and a lot of the rest of the nitty-gritty is missing. Through informed imagination, much of that can be restored. And it’s like learning to read music. The point is not just to grasp the grammar and the syntax but to envision, and maybe re-create, a genuine performance.

The typescript looks at first to be plain prose, which is a form designed to minimize the outward individuality of any human voice. Almost no one speaks in genuine prose, but the form is often used – by journalists, linguists, and court reporters alike – for transcriptions. The typographic form we associate with prose makes speakers look like writers.

Swanton went looking for what he couldn’t see, and his typewritten texts are the result. I went looking, in the typescript, for what I couldn’t hear: the oral art, the form and meaning hidden in the flattened landscape of the page.

(p. 188 in the same essay.) He reproduces a portion of the typescript, demonstrating his point:

illustration from p189 from the tree of meaning

There’s a lot to think about here, especially now. Each technology in its own way dictates a Procrustean bed, though we’re often not attuned to what the constraints of our technology are. The high-bandwidth networked screen creates possibilities: more can be passed along in the transmission of stories than was before. But constraints dictate form: we know how to read the print book perhaps because that extra information has been sheered away. Learning to read electronically may be complicated.

changes

You’ve probably noticed that things have been relatively quiet around here lately. I haven’t been on vacation or anything like that. Rather I’ve been figuring out the future, not of the book, but of me. After much personal consideration, and discussion with the group here, I’ve decided that now’s the time for me to move on from the Institute after three and a half fantastic years. I’ll still be a part of the general Institute community, and will continue posting here periodically, but as of now my leadership, management and production roles will be phased out. I’m not yet sure where I’m headed next.
It’s surreal looking back on the beginning of this place, and of this blog. I came to this work as sort of a blank slate, a liberal arts refugee (to borrow a term of Dan’s), a theater major a couple of years out of college with practically no knowledge or experience in the field of new media and the Web, but deeply interested in the questions we were asking, and I suppose blessed with a naiveté that enabled me to jump headlong into new territory without knowing what the hell I was doing. There’s an old rabbinical adage from somewhere: “do first, understand later.” Not that I fully understand now, but I’ve definitely learned a thing or two.
This blog has been a deeply rewarding, at times agonizing place of discovery for me, a way of educating myself publicly. I thank everyone who has taken the time to read my thoughts, ramblings and observations here, and especially those who have weighed in in the comment stream, which is where so much of the thinking gets refined, corrected and improved. Finally, I thank my colleagues past and present who have been so smart, so challenging and, above all, so different from me, which is what has always made this such an interesting place.
I plan to continue in this field (whatever you call it – ?publishing, new media, web stuff…), and also to pursue other interests that have reawakened during my time here (namely that most unmediated of art forms, live theater). It may be a little while before I settle on my next big project. I welcome any ideas and advice.
Lest I get too elegaic, I’ll stop there. More regular posting should resume before too long.

a la recherche

I was on the underground making my way to the London Book Fair yesterday, hoping to stand out from the crowds of frantic publishers jostling there by carrying over my shoulder the fabulously pretentious “Proust Society of America” book bag which I bought on a trip to New York for a meeting at the Mercantine Library, but was disconcerted to notice that the man on the other side of the carriage was staring at me strangely, then eventually he lent over and said to me, “Have you read Proust?” to which I replied yes I had, most of it, but many, many years ago, at which this gentleman told me that on his retirement he had made a list of classics he hadn’t read, and In Search of Lost Time was top of it so he has since read it six times, on permanent rotation, breaking off between volumes for other novels and recently he’s been looking for a Proust close reading group, has scoured the internet for such a thing, had found the New York group but nothing like it in London; then we arrived at Holborn Station and he stepped off the train before I could ask to swap email addresses, not because I want to start a close reading Proust group, but… well, perhaps he’ll Google his way to this page, and perhaps some other London Proust lovers will too and then I can put them in touch with each other and so the Marcel Proust Underground Networked Book Group will be born.

old school

J.K. Rowling went to court today to try to stop someone from publishing a lexicon of Harry Potter characters. She says she wants to do it herself, but even if that gave her the right to stop others from doing it (which i surely hope is not what the court decides), Rowling misses the opportunity here to JOIN with Harry Potter fans in the sublime exercise of building on the story.
Reminds me of a koan i’ve been working on which goes like this:
old school authors commit to engage with a subject ON BEHALF of future readers.
new school authors commit to engage WITH readers in the the context of a subject.

thinking about tex

Chances are that unless you’re a mathematician or a physicist you don’t know anything about TeX. TeX is a computerized typesetting system begun in the late 1970s; since the 1980s, it’s been the standard way in which papers in the hard sciences are written on computers. TeX preceded PostScript, PDF, HTML, and XML, though it has connections to all of them. In general, though, people who aren’t hard scientists don’t tend to think about TeX any more; designers tend to think of it as a weird dead end. But TeX isn’t simply computer history: it’s worth thinking about in terms of how attitudes towards design and process have changed over time. In a sense, it’s one of the most serious long-term efforts to think about how we represent language on computers.
TeX famously began its life as a distraction. In 1977, Donald Knuth, a computer scientist, wanted a better way to typeset his mammoth book about computer science, The Art of Computer Science, a book which he is still in the process of writing. The results of phototypesetting a book heavy on math weren’t particularly attractive; Knuth reasoned that he could write a program that would do a better job of it. He set himself to learning how typesetting worked; in the end, what he constructed was a markup language that authors could write in and a program that would translated the markup language into files representing finished pages that could be sent to any printer. Because Knuth didn’t do anything halfway, he created this in his own programming language, WEB; he also made a system for creating fonts (a related program called Metafont) and his own fonts. There was also his concept of literate programming. All of it’s open source. In short, it’s the consummate computer science project. Since its initial release, TeX has been further refined, but it’s remained remarkably stable. Specialized versions have been spun off of the main program. Some of the most prominent are LaTeX, for basic paper writing, XeTeX, for non-Roman scripts, and ConTeXt, for more complex page design.
How does TeX work? Basically, the author writes entirely in plain text, working with a markup language, where bits of code starting with “” are interspersed with the content. In LaTeX, for example, this:

frac{1}{4}

results in something like this:

onequarter.gif

The “1” is the numerator of the fraction; the “4” is the denominator, and the frac tells LaTeX to make a top-over-bottom fraction. Commands like this exist for just about every mathematical figure; if commands don’t exist, they can be created. Non-math text works the same way: you type in paragraphs separated by blank lines and the TeX engine figures out how they’ll look best. The same system is used for larger document structures: the documentstyle{} command tells LaTeX what kind of document you’re making (a book, paper, or letter, for example). chapter{chapter title} makes a new chapter titled “chapter title”. Style and appearance is left entirely to the program: the author just tells the computer what the content is. If you know what you’re doing, you could write an entire book without leaving your text editor. While TeX is its own language, it’s not much more complicated than HTML and generally makes more sense; you can learn the basics in an afternoon.
To an extent, this is a technologically determined system. It’s based around the supposition of limited computing power: you write everything, then dump it into TeX which grinds away while you go out for coffee, or lunch, or home for the night. Modern TeX systems are more user friendly: you can type in some content and press the “Typeset” button to generate a PDF that can be inspected for problems. But the underlying concept is the same: TeX is document design that works in exactly the same way that a compiler for computer programs. Or, to go further back, the design process is much the same as metal typesetting: a manuscript is finished, then handed over to a typesetter.
This is why, I think, there’s the general conception among designers that TeX is a sluggish backwater. While TeX slowly perfected itself, the philosophy of WYSIWYG – What You See Is What You Get – triumphed. The advent of desktop publishing – programs like Quark XPress and Pagemaker – gave anyone with a computer the ability to change the layouts of text and images. (Publishing workflows often keep authors from working directly in page layout programs, but this is not an imposition of software. While it was certainly a pain to edit text in old versions of PageMarker, there’s little difference between editing text in Word and InDesign.) There’s an immediate payoff to a WYSIWYG system: you make a change and its immediately reflected in what you see on the screen. You can try things out. Designers tend to like this, though it has to be said that this working method has enabled a lot of very bad design.
(There’s no shortage of arguments against WYSIWYG design – the TeX community is nothing if not evangelical – but outside of world of scientific writing, it’s an uphill battle. TeX seems likely to hold ground in the hard sciences. There, perhaps, the separation between form and content is more absolute than elsewhere. Mathematics is an extremely precise visual embodiment of language; created by a computer scientist, TeX understands this.)
As print design has changed from a TeX-like model to WYSIWYG, so has screen design, where the same dichotomy – code vs. appearance – operates. Not that document design hasn’t taken something from Tex: TeX’s separation of content from style becomes a basic principle in XML, but where TeX has a specific task, XML generalizes. But in general, the idea of leaving style to those who specialize in it (the designer, in the case of print book design, the typesetting engine in TeX) is an idea that’s disappearing. The specialist is being replaced by the generalist. The marketer putting bulletpoints in his PowerPoint probably formats it himself, though it’s unlikely he’s been trained to do so. The blogger inadvertently creates collages by mixing words and images. Design has been radically decentralized.
The result of this has been mixed: there’s more bad design than ever before, simply because there’s more design. Gramsci comes uncomfortably to mind: “The crisis consists precisely in the fact that the old is dying and the new cannot be born; in this interregnum a great variety of morbid symptoms appear.” If TeX comes from an old order, it’s an order with admirable clarity of purpose. Thinking about TeX points out an obvious failure in the educational system that creates the current environment: while most of us are taught, in some form or another, to write, very few are taught to visually present information, and it’s not clear that a need for this is generally perceived. If we’re all to e designers, we have to all think like designers.