Cloud Atlas

I recently finished reading Cloud Atlas by David Mitchell, a novel split into six interlocking stories that spans from a 19th-century maritime adventure to a near- and post-apocalyptic sci-fi future. There's much to like about the book, but since I'm such a structure-fiend I'll mostly stick with a surface description of the layout.
The book is designed to be read in the form of a queue stack: first-in, first-out last-out. I.e., the book starts with the first story, which is interrupted by the second story, which is interrupted by the third story, until we get to the complete sixth story, which is then followed by the conclusion to the fifth story, which is followed by the end of the fourth story, until the book ends with the conclusion of the first story. It looks sort of like this:
While the six stories vary greatly in place, time, genre, and prose (Melville-like, Victorian novel, pulp fiction, Hollywood movie, sci-fi, Faulkner sci-fi), they are of course linked thematically and narratively. So the diary from the first story is found by the composer in the second story whose letters are sent to a protagonist in the third story which is a novel being read by a publisher in the fourth story, and so on. The novel does its best to logically explain the start and end of each segment to the activities of the characters in the neighboring stories.
While I can't say Mitchell is a master of all the genres he writes in here, it is the case that the disappointment I had at the beginnning of a new segment turned into compelling interest by the time the next rolled around, until I was juggling five cliffhangers in my mind during the sixth and central story. The cliffhangers unwind methodically, rationally, and almost too satisfyingly, but the end result is a well-written novel for the impatient reader.
There's much to say about the characters, themes, and prose but instead I'll point you to The Guardian's rave review and The New York Times tepid review and say that my opinions lie somewhere in between.
<<< October Surprise Best of the Las Vegas Valley 2006: Food & Drink choices >>>

Hey, I just finished the chapter in Godel, Escher Bach dealing with recursion and he's got a "dialogue" or short story written in that format... of course in GEB, he ends it on the wrong level which is intentionally frustrating.
Ah yes, I should've remembered that dialogue. I think I left my copy of GEB back in Cambrige.
Funny, I was just talking about frame stories within frame stories the other day because someone left a set of the Harvard Classics on our lawn, and as such I started reading from the arabian nights, which does this excessively.
Italo Calvino did it too in "If on a winter's night a traveler..." Except I'm not sure he gave endings for all his stories. I think it was also intentionally frustrating.
If on a winter's night... is a beautiful book. Except I must admit I've been meaning recently to go back and look again at how it all works out, because I can't quite reconstruct it in my head- isn't it labrynthine more than a series of frames?
you mean 'first in, last out'?
you're right. it's a stack. i've been apart from data structure textbooks for too long.
jon may, you should've caught that as well. i think you've been too busy studying computational language that you've forgotten your CS roots.
Ha, I figured you were just using some computer science alternate phrase for a stack so I kept my mouth shut.
I like how you've turned this into my fault for not saying anything, rather than yours for making the mistake in the first place. After all, you do have more time spent as a CS student than I do, so far.
Post new comment