The Future Does Not Compute: Transcending the Machines in Our Midst
Author: Stephen L. Talbott
Publisher: O'Reilly & Associates
ISBN: ISBN 1-56592-085-6
Reviewer: Danny Yee
At heart The Future Does Not Compute is an attack on the excesses of technological optimism, particularly those associated with computers. Talbott is worried about the identification of technology with the ends it is supposed to help us achieve (of communication systems with community, for example) and with what our growing reliance on technology indicates about ourselves: he sees computers as bringing out the worst in people and as a kind of reflection of a wider malaise. Part one is a broad survey of the relationship between computers and human communities (which wanders as far afield as globalization and business ethics); part two considers the effects of computers in education; part three is about the effects of computers on writing and language and on the elevation of “information” to an end in itself; and the final part is about the “evolution of consciousness”.
I got about two thirds of the way through The Future Does Not Compute before giving up on it. It wasn't its anti-technological stance which turned me off, but rather the way Talbott went about presenting his ideas. All too often he lapses into complete mysticism, with such outbreaks as
The solitary bird, gripped by an unknowing intensity as it ploughs through the trackless ether, hears, on the dull edges of its consciousness, a call of destiny sung by hidden choirs.
(which is defended by a counter-attack on a ridiculous straw-man reductionism). Even where he avoids outright obscurantism, Talbott lacks any kind of respect for philosophical niceties. He keeps on attributing intentionality to machines, for example, in such fashion as
the computer ups the ante in a game already extremely perilous. It relentlessly, single-mindedly, apes us even in those habits..., for it is endowed in some sense with a mind of its own.
and talks about them “acting in their own right”, but at the same time refuses to allow that there is any sense in which they can approach human beings. For all he goes on about the “mechanical” being present in our “inner selves”, Talbott's rhetoric relies heavily on a rigid and fundamental dichotomy between the natural and the artificial, between man and machine. He makes no attempt at all to justify this assumption: even the references to Searle and Penrose I kept expecting never turned up.
Talbott has an eye for an effective phrase and an impressive vocabulary (sometimes he verges on poetry), but this is taken to extremes: he is always prepared to sacrifice clarity and content on the altar of rhetoric and effect. Terms like “human nature” and “consciousness” and phrases such as “our trust as stewards of the Earth” and “sleepwalking subservience to technology” are used without any explanation in critical contexts. Here are some longer examples:
We must tame technology by rising above it and reclaiming what is not mechanical in ourselves.
Where, as a child, I differentiated myself from the animal, now I must learn to differentiate myself from the machine—and this differentiation lies in the deepening of consciousness. It is therefore not only a matter of pointing to established human nature; it is also a matter of realizing human nature in its movement toward the future. Related problems are that Talbott presents his ideas in a rambling and disconnected fashion, in short sections within short chapters, and that he has a tendency to say the same thing over and over again in different ways.
The Future Does Not Compute also lacks any kind of sociological or psychological depth. The discussion of globalization, for example, doesn't engage at all with historical or economic perspectives on the subject, and analysis of at least one concrete example (of a network group which claims “community” status) might have given some basis to his analysis of the relationship between technology and community; as it is, all he can offer on these subjects are empty generalizations.
The most distressing thing about The Future Does Not Compute is that I actually agree with quite a lot of what Talbott has to say, both on general subjects like education and the evils of assuming there are technological solutions to all human problems and on more specific ones such as profit-seeking business ethics and naively optimistic claims by artificial intelligence researchers. I fear, however, that many people will use his book as another excuse to reject all discussion of some important questions as obscurantist nonsense. In the end I abandoned The Future Does Not Compute because I wasn't learning anything from it: it is emotionally stirring but intellectually vacuous.
Disclaimer: I requested and received a review copy of The Future Does Not Compute from O'Reilly & Associates, but I have no stake, financial or otherwise, in its success.
All book reviews by Danny Yee are available via anonymous FTP ftp.anatomy.su.oz.au in /danny/book-reviews (index INDEX) or URL www.anatomy.su.oz.au/danny/book-reviews/index.html Copyright © Danny Yee 1995. He can be reached via e-mail at firstname.lastname@example.org. Comments and criticism welcome.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Roll your own dynamic dns
2 hours 58 min ago
- Please correct the URL for Salt Stack's web site
6 hours 9 min ago
- Android is Linux -- why no better inter-operation
8 hours 24 min ago
- Connecting Android device to desktop Linux via USB
8 hours 53 min ago
- Find new cell phone and tablet pc
9 hours 51 min ago
11 hours 20 min ago
- Automatically updating Guest Additions
12 hours 28 min ago
- I like your topic on android
13 hours 15 min ago
- This is the easiest tutorial
19 hours 51 min ago
- Ahh, the Koolaid.
1 day 1 hour ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?