Review:
Anathem, by Neal Stephenson
| Publisher: |
William Morrow |
| Copyright: |
2008 |
| ISBN: |
0-06-147409-6 |
| Format: |
Hardcover |
| Pages: |
935 |
Fraa Erasmas is a little less than twenty years old and is an avout of the
decade math of the Concent of Saunt Edhar. As
Anathem opens, he's
approaching his first apert. All of those words are left for the reader
to puzzle out for themselves, unless you cheat and read the glossary
(which I would recommend doing only with caution, but more on that in a
moment), since Erasmas, the first-person narrator of this story, writes
(mostly) as if the reader is familiar with the mathic world and its
concepts.
Translated into English, it means that Erasmas was brought into something
akin to a scientific monastery (the "math") at around the age of nine and
has been there for ten years, since his math is a decade math and
therefore remains closed to all outside (s cular) ideas and contact for
periods of ten years at a time. He is still a student there, not yet
declaring allegiance to one of the chapters. That's something that he
will be expected to do after the first apert. Every ten years, the decade
math opens its doors to the outside world for a period of ten days
(apert), and the fraas and suurs can leave the math and travel through the
outside world as they wish.
The start of
Anathem is an exercise in alienation and
reorientation. Stephenson has constructed a complex society with a long
history and its own specific technical jargon and throws the reader into
it with a minimum of orientation. Despite being familiar with SF novels
that use this technique, I did read the preface and recommend that other
readers do as well unless they particularly love piecing together a world
from hints and clues. The timeline, in particular, was invaluable and
something I referred to throughout the story. But even with the preface,
you should expect to read the first part of
Anathem interpolating
meanings from context or just letting things slip past until you later
come to understand them.
A lot of people bounce off of
Anathem here, and it's one of the
reasons why I'd been postponing reading it (the other being that it's a
substantial doorstop and I wanted to give it my undivided attention). But
it's really not as bad as I feared. One gets a feel for the terms fairly
quickly, and the more difficult ones Stephenson defines as he goes with
excerpts from a dictionary of the mathic world. I found it slightly
disorienting for a chapter or two, and then it started growing on me. The
terminology is sometimes different just for the sake of being different
(jeejahs are indistinguishable from smartphones for all practical
purposes), but usually the invented words provide either important links
to the past of the constructed world of Arbre or are technical terms that
add precision and clarity once you know their meanings. It can be a
little bit frustrating to remember the mapping of famous theories and
theorems to the Orth names, but only mildly. (And Diax's Rake is so
useful of a name for something that English doesn't name that I may start
using it myself.)
This is also why I recommend against reading the glossary. The
definitions of terms are linked to important parts of history, which are,
in turn, linked to important parts of the plot, and the glossary therefore
risks spoilers. I liked having the term introduced by the frequent
dictionary excerpts scattered through the chapters, and enjoyed the
feeling of the terminology unfolding with the plot. The glossary is there
if you really get lost, but I think the experienced SF reader
(particularly if you have enough history background to pick up on the
obvious parallels and start mapping bits to Greece, Rome, the Catholic
Church, etc.) will be able to navigate the language without that much
difficulty.
I also stopped caring about the terminology because the story is so
engrossing that it pulled me right into the book, closed over me, and
made Erasmas's world feel real, precious, and fascinating. Whether that's
going to be true of other people is a surprisingly difficult question, and
one that I'll try to tackle as part of this review. But I will say
up-front that I think this is the best book that Stephenson has ever
written, even better than
Snow Crash,
despite some undeniable flab and one extremely irritating choice.
Anathem is, at its heart, a novel about the scientific method. I
think it's the first book by Stephenson that elegantly mingles his
tendencies (and obsessions) as a writer with the interests (and
obsessions) of the characters and makes the whole novel feel coherent.
All of Stephenson's books are prone to discursive infodumps, but they've
usually had to be shoehorned in around the characters. Even with the
Baroque Cycle, a series full of natural philosophers, the
digressions are jammed in around the plot like the filling of an
over-packed box and frequently stick out at odd angles or dribble out on
the floor. With
Anathem, Stephenson has populated a book full of
characters who have completely believable and engrossing reasons to
digress into scientific debate and analysis, can put them into dialogue
and thereby avoid some of the strain of the infodump, and (most
importantly) largely restrains himself from narrative digressions via
first-person narration and careful attention to when the characters
themselves would follow the same digression.
In short, this is a book full of very smart and very well-educated people
who figure things out from first principles using agreed-upon theory,
thrown into an unknown and dangerous situation that requires a great deal
of deep thinking, science, engineering, and philosophy. All of
Stephenson's quirks are still here, on prominent display, but rarely have
I ever seen a better match of writer, characters, plot, and world
background than this book. I would go so far as to say that, if you don't
like this book, you're unlikely to like any long Stephenson.
I haven't said a lot about the plot. Erasmas's apert is only the first
part, and barely touches on any significant plot elements. It's mostly
there to set some groundwork, introduce characters, and get the reader
oriented. I'm not going to say much more, since the way the novel
transitions from routine to unusual to emergency, and the resulting
scramble to understand the emergency, is the heart and soul of this book
and should not be spoiled. (I spoiled myself slightly by reading some
analysis that I shouldn't have and regretted it, although it wasn't too
much of a problem.) This is one of Stephenson's best-plotted novels. It
develops slowly enough for the reader (and the characters) to think hard
about it and make some good and bad guesses, but fast enough to stay
engrossing. Most of it is very well-paced provided that you find the
background of science and philosophy of science interesting. (If you
don't, this is probably not a book you're going to enjoy.)
I say "most of it" because, as mentioned earlier, this book is a bit
flabby. There are a couple of sections where the theory and analysis are
pushed aside by exigent circumstances and more action-oriented plot
elements, both of which reminded me that Stephenson is very bad at writing
action sequences and both of which I wished were shorter. And there are a
couple of sections where Erasmas is getting oriented to a new situation or
working up the courage to do something where I wished he'd get on with it
already. But for a novel of nearly 1,000 pages, the amount of tension and
reader interest Stephenson maintained for me was quite impressive.
But as good as the plot is, the best part of this book is its full-bore,
no-apologies embrace of
understanding things. This is a book about
making sense of the world, and about what it means to make sense of the
world, and how you go about it, and what preconditions are required to do
so. It is not, contrary to so much science fiction, a book about knowing
things. The people who are already experts appear in this book, but
generally only in the context of figuring out new things they've not
previously been exposed to. Rather, it's a book about learning things,
the thrill that comes from applying theory to understand something new,
and the satisfaction of working through something from first principles or
previously-established theory, arriving at testable predictions, and then
testing them. It's the first novel I've read that captures some of the
joy and delight that I got from reading George Gamow's
One Two Three... Infinity as a child.
Stephenson novels have always been about showing the reader neat things he
learned, but I think previous books relied on the reader to bring their
own enthusiasm.
Anathem, at least for me, goes a step farther and
uses the passion and approach of its characters to
create that
enthusiasm. It's one of those books that I not only enjoyed but went away
from feeling like it made me a better person in some subtle but detectable
way.
Sadly, this is also where the irritating part comes in.
I'm going to be very careful and indirect here, since the details are all
extremely significant spoilers. You may want to skip to the last
paragraph of this review if you want to avoid any knowledge about the end
of
Anathem.
Stephenson pulls several rabbits out of the hat in this book, but most of
them are well-defended and nicely handled bits of misdirection. There are
a few where I thought the science or engineering was dubious, but even
those are usually backed with enough hand-waving about Arbre technology
that I could swallow it enough for the purposes of this book. (The
timeline here is very helpful in allowing one to write off a few things as
unknown technology.) But he puts, at the core of the plot, one of the
most scientifically dubious bits of the whole book, and there's simply no
avoiding that by the end of the story.
Now, this doesn't mean that he just expects the reader to swallow it.
Much of
Anathem is a carefully-constructed defense of the bits he
uses for the plot, and the defense is not half-bad within his fictional
world. There are substantial in-book justifications for believing these
techniques will work on Arbre even if they wouldn't in our scientific
domain. So it's not so much the plausibility that bothered me; the idea
is at least as plausible as some of the FTL drive concepts that I've
swallowed without complaint. I do hold
Anathem to a higher
standard because the book is about science in a way that most science
fiction isn't, but even with that, I think Stephenson mostly managed to
dance across the thin ice he built.
The problem is more subtle but more serious: if taken seriously on its own
terms, the approach Stephenson takes to the plot destroys science in his
universe.
I can't really say more than that, since all of the details are huge
spoilers, but the more I thought about it, the more irritated and annoyed
I got.
Anathem is otherwise a brilliant defense of the scientific
method, and it felt like Stephenson injected a poison pill in the center
of it, leading necessarily to a world where the scientific method no
longer works. This does not happen on camera, or even between the pages
of the book; you have to think about the implications for a while before
you realize that's what happened. But once you do, it's a bitter pill to
swallow, and it's hard to escape the feeling that it fundamentally
undermines Stephenson's whole project here. And, to make it worse
(although also oddly better in a way), I think it was unnecessary. He
would have had to reconstruct the ending, but I can't shake the feeling
that there were ways to write the ending, even maintaining the same
character strengths, without having to pull that particular rabbit out of
the hat.
Because I think it's, in the end, unnecessary, I was still able to enjoy
the whole book, including the ending, despite this, but while the rest of
Anathem is a wholehearted 10, that choice knocked a full point off
my impression of the book. It's profoundly irritating precisely because
Stephenson did such an excellent job with the rest of it.
But, that said, this book is still exceptional. I think it's the book
that Stephenson was meant to write. Not only did he get the overall
construction nearly perfect, he gets so many of the details right, from
the history (which for a while I thought was merely clever, once I started
seeing the correspondences that moved it out of the realm of pure
invention, but which transitioned back to profound with later revelations
in the book) to the language to the way that he excerpted some theoretic
digressions into very well-done appendices. If you've ever thought of a
theory as beautiful, or like reading about smart people debating the
nature of understanding and knowledge, I cannot recommend this book too
highly. Despite the highly irritating flaw at its center, and despite a
few sections that show Stephenson is not a well-rounded writer, I think
it's brilliant.
Rating: 9 out of 10
My friend Noah mentioned the game VVVVVV. I was confused because I thought he was talking about the visual programming language vvvv. I went to Wikipedia to clear up my confusion but ended up on the article on VVVVV which is about the Latin phrase vi veri universum vivus vici meaning, by the power of truth, I, while living, have conquered the universe .
There is no Wikipedia article on VVVVVVV. That would be ridiculous.
Today was my "clean the house" day. I made a start, then went for my
chiropractic assessment and adjustment. I now only need to see him fortnightly,
which is nice. I knocked out most of the cleaning, and then went for a massage
and had some lunch. The next thing I knew it was about time to pick up Zoe.
I biked to Kindergarten, and she was asleep again. She woke up reasonably
easily, but was grumpy not long after that. She was very uncooperative, and
didn't want to go home on the bike, and wouldn't let me put sunscreen on her.
After a bit of work, I managed to extract from her that she didn't like my
"sweaty hands" from riding the bike there, so I washed my hands and then she
let me sunscreen her up. I'll try doing pick ups in the car next week I think.
We got home, and I needed to get some more kitty litter, so we went out to Pet Barn. Zoe had a great time checking
out all the fish, and also playing with aquarium decor. It got me thinking that
maybe an aquarium might be a good birthday present for her, if not this year,
maybe next year. It turns out that fish aren't particularly expensive, so
they'd make for easy presents for people.
After that, we popped across to Bunnings, because I needed a couple of things.
While we were there, Zoe announced she wanted to go to the toilet, so we
started trekking off to where I thought the toilets were. Turned out I was
wrong, and they were at the opposite end of the building, so we had to trek all
the way back again. Zoe got all the way into the ladies bathroom and failed to
make it onto the toilet in time, so that concluded our visit to Bunnings.
We got home and she got changed, and I started making dinner. While dinner was
cooking, Zoe watched a bit of TV, and then I decided to try making some lunch
box pies, essentially a piece of buttered bread jammed into a muffin tray with
some creamed corn and bacon in the bottom and beaten egg on top, thrown in the
oven. Zoe helped sample the bacon and cracked the eggs for me, while I buttered
bread and cut the crusts off and jammed slices into muffin trays.
Bedtime was remarkably uneventful for a change.
I m looking forward to building up the bicycle over the next couple months and I ll post more pictures when it s finished. I am blown away by Marty s craftsmanship and attention to detail. I am psyched that his donation made this bike possible and that I was able to get the frame while helping cycling in Massachusetts!
The radio silence here on my blog has been not from lack of activity, but the inverse. Linux.conf.au chewed up the few remaining spare cycles I have had recently (after family and work), but not from organising the conference (been there, got the T-Shirt and the bag). So, let s do a run through of what has happened
LCA2014 Perth has come and gone in pretty smooth fashion. A remarkable effort from the likes of the Perth crew of Luke, Paul, Euan, Leon, Jason, Michael, and a slew of volunteers who stepped up not to mention our interstate firends of Steve and Erin, Matthew, James I, Tim the Streaming guy and others, and our pro organisers at Manhattan Events. It was a reasonably smooth ride: the UWA campus was beautiful, the leacture theatres were workable, and the Octogon Theatre was at its best when filled with just shy of 500 like minded people and an accomplished person gracing the stage.
What was impressive (to me, at least) was the effort of the AV team (which I was on the extreme edges of); videos of keynotes hit the Linux Australia mirror within hours of the event. Recording and live streaming of all keynotes and sessions happend almost flawlessly. Leon had built a reasonably robust video capture management system (eventstreamer on github) to ensure that people fresh to DVswitch had nothing break so bad it didn t automatically fix itself and all of this was monitored from the Operations Room (called the TAVNOC, which would have been the AV NOC, but somehow a loose reference to the UWA Tavern the Tav crept in there).
Some 167 videos were made and uploaded most of this was also mirrored on campus before th end of the conference so attendees could load up their laptops with plenty of content for the return trip home. Euan s quick Blender work meant there was a nice intro and outro graphic, and Leon s scripting ensured that Zookeepr, the LCA conference manegment software, was the source of truth in getting all videos processed and tagged correctly.
I was scheduled (and did give) a presentation at LCA 2014 about Debian on Amazon Web Services (on Thursday), and attended as many of the sessions as possible, but my good friend Michael Davies (LCA 2004 chair, and chair of the LCA Papers Committee for a good many years) had another role for this year. We wanted to capture some of the hallway track of Linux.conf.au that is missed in all the videos of presentations. And thus was born LCA TV.
LCA TV consisted of the video equipment for an additional stream mixer host, cameras, cables and switches, hooking into the same streaming framework as the rest of the sessions. We took over a corner of the registration room (UWA Undercroft), brought in a few stage lights, a couch, coffee table, seat, some extra mics, and aimed to fill the session gaps with informal chats with some of the people at Linux.conf.au speakers, attendees, volunteers alike. And come they did. One or two interviews didn t succeed (this was an experiment), but in the end, we ve got over 20 interviews with some interesting people. These streamed out live to the people watching LCA from afar; those unable to make it to Perth in early January; but they were recorded too and we can start to watch them (see below)
I was also lucky enough to mix the video for the three keynotes as well as the opening and closing, with very capable crew around the Octogon Theatre. As the curtain came down, and the 2014 crew took to the stage to be congratulated by the attendees, I couldn t help but feel a little bit proud and a touch nostalgic memories from 11 years earlier when LCA 2003 came to a close in the very same venue.
So, before we head into the viewing season for LCA TV, let me thank all the volunteers who organised, the AV volunteers, the Registration volunteers, the UWA team who helped with Octogon, Networking, awesome CB Radios hooked up to the UWA repeated that worked all the way to the airport. Thanks to the Speakers who submitted proposals. The Speakers who were accepted, made the journey and took to the stage. The people who attended. The sponsors who help make this happen. All of the above helps share the knowledge, and ultimately, move the community forward. But my thanks to Luke and Paul for agreeing to stand there in the middle of all this madness and hive of semi structured activity that just worked.
Please remember this was experimental; the noise was the buzz of the conference going on around us. There was pretty much only one person on the AV kit my thanks to Andrew Cooks who I ll dub as our sound editor, vision director, floor manager, and anything else. So who did we interview?
A few hours ago I posted about share-file, a small tool to make a local file available at a public URL so that it is transferred from my machine, without being stored at some central server. I wanted to create something like FileTea, but usable from the command line.
My post made it to HackerNews (which brought my server to its knees for a while; let s say I had the opportunity to find out what setting for apache s MaxClient option works on my machine...), where the comments (besides some misunderstanding about the notable features of share-file) contained interesting links related to solving #949:
here's the list of RC bugs I've worked on during the last week.
I defended my dissertation three months ago. Since then, it feels like everything has changed.
I ve moved from Somerville to Seattle, moved from MIT to the University of Washington, and gone from being a graduate student to a professor. Mika and I have moved out of a multi-apartment cooperative into into a small apartment we re calling Extraordinary Least Squares. We ve gone from a broad and deep social network to (almost) starting from scratch in a new city.
As things settle and I develop a little extra bandwidth, I am trying to take time to get connected to my community. If you re in Seattle and know me, drop me a line! If you re in Seattle but don t know me yet, do the same so we can fix that!
Many protocols today allow you to upgrade to TLS from within a cleartext version of the protocol. This often falls under the rubric of "STARTTLS", though different protocols have different ways of doing it. I often forget the exact steps, and when i'm debugging a TLS connection (e.g. with tools like