So . . . Cryptonomicon by Neal Stephenson

[pegkerr]

I've heard that this book is excellent.

Um, how much do I have to read before it actually becomes interesting? I'm willing to keep going, but for how long?

Edited to add: It just occurred to me that I probably don't want to start such a long book the week before the next Harry Potter book comes out, so I'm putting it aside and will try again after I've read HPHBP.

Comments

[jonquil.livejournal.com]

It may not be your book. It's my book because I care passionately about cryptography and the sainted Alan Turing and sprockets that are relatively prime. But if Stephenson's geekery is not your geekery, I can't think why you'd read it. It's an extended software-industry in-joke. Do not get me wrong, I love the book with a white-hot passion.

Did you like *Snow Crash*? If not, I wouldn't expect you to like Cryptonomicon.

[pegkerr.livejournal.com]

Haven't read Snow Crash. This is the first Neal Stephenson book I've tried.

[jonquil.livejournal.com]

One of the great pleasures of maturity is that you can stop reading a book any damn time you want to. Who cares whether you *should* like it?

::looks nervously at the pile next to her bed::

[wintersweet.livejournal.com]

I really, really enjoyed _Snow Crash_, but _Cryptonomicon_ completely failed to get my attention.

[rolanni.livejournal.com]

I loved Snow Crash and pressed it upon all of my friends, some of whom are still speaking to me. Cryptomonicon so much failed to interest me that I'm not even sure I've spelled it right, much less tried to read it. One of the friends I infected with Snow Crash, however, is a Serious cryptographyy geek, and loves all things computational. Cryptowhatsis is his Perfect Book -- and he was kind enough not to insist that I read it *g*