Every week, Criticwire asks film critics a question and brings you their responses in The Criticwire Survey. We also ask each member of the poll to pick the best film currently playing in theaters. The most popular choices can be found at the bottom of the post. But first, this week's question:
Q: In cases where a film is based on a book — like "Gangster Squad," opening this Friday and based on a book by Paul Lieberman — do you prefer to read the book before seeing the movie, or avoid the book until after you've reviewed it?
"It really depends. There are some movies where I race to finish the book before I see the movie; I wanted to re-read 'Cloud Atlas,' for example, before I watched it. And then there are some books where I'm indifferent to reading the book afterward. If I sense something is lost from the film version or I'm interested in the author, I usually check out the book."
"I'm going to punk out and say that it depends upon the writer of the movie. I'm always curious what decisions the writer of the movie made when adapting it. So, for example, I read the book 'One Shot' after seeing 'Jack Reacher,' because I wanted to see Christopher McQuarrie's influence on the project. But for a movie that I expect the writer not to matter so much, or even something like 'Sin City' that is slavishly devoted to the book, I may read the book first or not at all."
"The timing depends on the material. It certainly enriches the experience of watching Visconti's 'Death in Venice' when you have read Thomas Mann in advance. The same goes for Kubrick's 'Eyes Wide Shut' and Schnitzler's 'Dream Story.' With whodunits it makes a lot of sense to wait, to see the way a film handles suspense. In some cases, it even works to sandwich the film in between. Last year, I picked up Nobel Prize winner Patrick White's 600 page novel 'The Eye of the Storm' in anticipation of Fred Schepisi's movie, saw the film, continued the novel, interviewed Geoffrey Rush and Schepisi, wrote about it, then continued reading the book."
"I used to always read the book first, but I'm not sure that's the best idea — it turns everything into a potential compare/contrast essay, though I often found that an adaptation's weaknesses were usually in its omissions. With a phenomenon book like 'Harry Potter' or 'The Da Vinci Code,' where your readers will most likely know it, I do think you owe it to them to know the source a bit. One thing nobody ever asks, though, is how many critics play the video game if a movie is based on one. I used to try to do that always too. Not so much lately."
"I don’t have a strategy either way regarding movies based on books. If I can read the book beforehand, depending on the subject matter, I will. Some filmmakers, frankly, rely too heavily on audiences having read the books that inspire their work, which is dangerous. A movie should be able to be satisfying separate of its source material; this audience reliance smacks of laziness to me. In the case of 'Gangster Squad,' I haven’t read the source material and hope director Ruben Fleischer can make a compelling film that will work for anyone who isn’t familiar with the topic at hand. I haven’t seen the film yet, so all I have to go on is hope, despite Warner Bros. moving 'Gangster Squad' to the dregs of January."
"My passion has always been for the medium of film and although I do appreciate the source material, I prefer to always watch the film before I check out the novel. I really hate spoiling plot points and details before watching a film and I would much rather have my first experience with the stories on a theater screen rather than reading a novel. However, if I really love a film, I sometimes check out the novel afterwards to see the differences and similarities from the adaptation. I've actually started an editorial on my website called 'Adaptation' which looks at the subject of book to screen. It will hopefully be more prominent in this new year."
"I prefer to avoid the book, unless I've read it of my own volition outside of the film being made. Too much importance is put on the notion of an adaptation and too little on how good the movie actually is. A movie adapted from any source should be a good movie first and a good adaptation last. So what I'm saying is 'first things first, then you can worry about panache later.'"
"I've actually gotten into many arguments regarding this topic. I've been lambasted over reading scripts, and books to a lesser extent, and 'ruining the experience' of the film, but I've always been more fascinated in how a director translates the written words to the screen. Recent examples include QT's 'Django Unchained' script and Dennis Lehane's 'Shutter Island' novel, but I didn't feel diminished returns after viewing the respective films, even with the twist in the latter. Read on!"
"I don't think a movie adaption should require me to read the book to understand it, so I don't consider it part of my duties as a reviewer to read the source book first. But I like to read. So, if a movie adaptation seems interesting, yes, I often read the book before seeing the movie. I find this usually enhances my viewing experience of the adaptation. Like, I know how I felt about the book, what it meant to me, what it's characters look and sound like to me. But I enjoy seeing what a filmmaker made of it. It's like a vivid book club discussion that I can revisit again and again, by watching the adaptation or reading the book. Sometimes it makes me like the movie better than I think I would have otherwise ('Cloud Atlas'), and sometimes it gives me a new appreciation for a story I didn't connect to when I read it ('Wuthering Heights'). Of course, sometimes the result is just me moaning, 'The book was so much better!' ('The Time Traveler's Wife')"
"Because I'm actually literally illiterate, I am almost always faced with the shame of seeing a novel (or self-help book) adaptation based on something I haven't read. (Or in the case of 'On the Road,' one I read at 16 and have next-to-no recollection of.) Every now and then I rally and tear through a book before seeing its movie. But that's not such a hot idea: I'll probably be more critical of what the film chucked or modified (or kept) than I should be (Such was the case with Stephen Frears' 'High Fidelity,' whose novel I finished roughly an hour before seeing it). If I can think of a case where it might be preferable to be basically ignorant of the source, I would actually argue for Pier Paolo Pasolini's 'Trilogy of Life,' namely 'The Decameron,' 'The Canterbury Tales,' and 'Arabian Nights.' Faced with, well, quite a lot of stories to adapt, he doesn't remotely try to be comprehensive. Instead he takes the stories that fit his particular interest. In this case, they tend to be the bawdy/saucy/sexy ones (Or as a friend pejoratively put it, 'the ones that Beavis and Butthead would have chosen'). For those who are intimately familiar with the originals, it can be understandably galling to see, e.g., Chaucer reduced to a proto-'Penthouse Forum.' However, that's reductive, too. Knowing the sources can also be conceivably distracting, as there's a lot more going on in Pasolini's renderings than just casual nudity, buttsex, and demons farting monks (an actual thing that happens in 'Canterbury'). Just to take one of its aspects, the matter-of-factness with which he presents sex and lust as a (mostly) happy, joyous activity is radical, in the 1970s and even today in our comparatively lax but still very Puritanical society. The potentially impossible utopia Pasolini presents is a world where complete nudity and carnality is not weird but casual and ever-present. And I'm not 100% sure that's in the Boccaccio, the Chaucer or the '1001 Nights.'"
"I don't go out of my way to actively do either, but since I cannot seem to put aside expectations once I've read something, I think it's better going in not having read the source material. The film should stand on its own."
"I like to read the book beforehand, if it's fiction, although that's not always possible. I've been bookworm my entire life, so in a lot of ways, books are my first love. They're two very different mediums, and it's justifiable to argue that they shouldn't be compared, especially in a review, but I find it fascinating to see how novels can be adapted for the screen in wildly different ways. Andrea Arnold's 'Wuthering Heights' is a prime example of this. On the other side of the spectrum is 'Savages,' which suffered from sticking a little too closely to some of the book's tics; O's narrative voice works better on paper, and even so would annoy some readers. And, of course, you have something like Julie Taymor's adaptation of 'The Tempest,' which changed Prospero to Propsera and starred Helen Mirren. I felt that Taymor didn't go nearly far enough in reinterpreting the text when presented with such a juicy opportunity. I admire her risk-taking and thought her version of 'Titus' was incredible, so 'The Tempest' was doubly disappointing."
"I prefer to read the book after I've seen and reviewed the movie. If I read the book first, I sit there noticing all the things they changed or cut out for the film, which can occasionally be a bit distracting. If I see the film first, I can sit back with the book and just enjoy reading all the added detail. This approach isn't always possible, of course, but in general, I find that it maximizes my enjoyment of both on their own individual terms."
"When it comes to films based on books, I used to want to read the book before the movie came out to get a better sense of what the story was and how characters were portrayed. This stems from my obsession with Stephen King at a young age and wanting to devour every word he put to paper before an adaptation. An example is 'The Stand,' which I read the huge extended edition, then watched the mini-series and wished the mini-series had a ton of the extended stuff, such as more of the Trash Can Man. The older I've gotten, the more I've actually stayed away from books before a movie comes out because I've realized I like to judge both on their own merits and flaws. I was happy to watch 'Children of Men' first, then read the book (which I thought was a bit boring and inferior to the film adaptation). Each are different in their own way, and when someone tries to adapt what people call a book that supposedly can't be done, like Cronenberg has done twice with 'Naked Lunch' and 'Cosmopolis.' But remember, as many kids never learn, you should never watch a movie for a book report. It never works and I've seen people get found out in the funniest ways. So in short, it depends on your preference, but I go with movie first, book second."
"I think of them as separate entities. I wouldn't avoid a book so as to go in fresh for the movie, but I wouldn't treat a book like homework for a movie either. Either I've read it, like 'Life of Pi' and 'The Rum Diary,' or I haven't, like 'The Hunger Games' and 'Cosmopolis.' What I want to know is, how the hell was 'Pitch Perfect' a book? 80 percent of the movie was rehearsals and a capella covers. Is the book just 50 pages of Blackstreet lyrics interspersed with snappy dialogue? Someone needs to read that and find out. Not me, but someone."
"I really don't have a strong point of view one way or the other. I rarely go out of my way to read the book of a film that's close to release, but if I'm already interested in the book I don't avoid it either. I even read scripts on occasion before the films come out, so I'm never especially worried about having a virginal cinematic experience with the material. I guess that's a long-winded way of saying I have no preference."
"You can read the book before or after seeing the movie — that's up to each individual reviewer — but I truly do think you have to read the book before writing a review. That's part of a critic's job — providing context, and giving the reader a sense of how the adaptation has been handled. That said, this is my 'perfect world' argument. In reality, there's only so much time in a day, and when most of us are doing this job for pennies and have other obligations, reading all the required books isn't realistic. My personal rule is this: if the movie is based on a more-or-less well-known property ('Life of Pi,' 'The Deep Blue Sea,' 'Midnight's Children,' etc.), I make a point of reading the source material (sometimes, of course, I've already read it.). If it's based on material few are aware of ('Silver Linings Playbook') or material of presumably limited literary merit ('Jack Reacher'), then I'll read it only if I have time (meaning: I probably won't read it). This year, for instance, I started reading 'Anna Karenina' in order to review the movie version, but it's such a freaking long book, and by the time the critics' screening came I'd only made it through a couple hundred pages. So I took the easy way out: I just didn't review it. I'm actually still reading the book — I'd always wanted to read it anyway — so if I don't finish it soon I may miss the movie entirely."
"I'm currently trying to get through 'Cloud Atlas' before the film is released over here in the UK this February. If I can, I'll always try and read the novel before seeing the adaptation, regardless of whether I'm reviewing the film or not. I always find that comparison much more satisfying, rather than embarking on the novel afterwards."
"Except in cases where memories of the book are impossibly ingrained in my consciousness (e.g. 'Cloud Atlas' or the 'Harry Potter' series), I try to separate the film and the book as much as possible. But I don't think seeing a film before I've had the chance to read the book impedes me in any way from enjoying the book just as much. If anything, the adaptation simply gives me a reading recommendation."
"I try to read books before they hit the screen for a few reasons: 1) I like having my own experience with a piece, before it is interpreted by someone else and 2) I feel it's important to know the work, as a benchmark, to be able to better compare and contrast what's onscreen. Of course, all that lofty talk being said, I don't always have the time for each read! Skimming can be a girl's best friend, she admitted, a bit embarrassed."
"I prefer to not read the book and go in cold, if I have not already read the book for my own enjoyment before. My general philosophy on such matters is that if the movie itself cannot be successfully viewed and understood on its own, separate from the book, then it is a failure as a film, and one of the best ways to judge this is to go in cold, with no knowledge of the book."
"I do whatever comes naturally, meaning if I haven't read the book, I usually don't seek it out necessarily. I enjoy reading criticism that compares films to their source material, but I also think sometimes it's best to look at the images and sounds as images and sounds. To retreat to an old party line, great books don't necessarily make great movies, and visa versa. That being said, I'm still waiting for someone to do the ultimate adaptation of Tanizaki's 'The Key.'"
"I review books based on films regularly for one of my outlets, so I grapple with this all the time. My theory: bad books make good movies. When the story is there, a film version can make it come alive. As for reading before seeing, I think it depends on the work. 'On the Road,' a recent adaptation of a major literary work can be seen before reading the book since no film can possibly capture the flavor of the dense and legendary novel. And, not to compare the sublime to the ridiculous, but you don't need to read Nicholas Sparks before seeing 'The Notebook,' 'The Lucky One,' or 'Dear John.' That said, some books need to be read before the screen version comes out. 'Perfume' and 'Notes on a Scandal' were two notable examples for me; the films touched on but never captured the strengths of those literary works. I do think pulp stories like 'Gangster Squad' can be translated to the screen — check out 'After Dark, My Sweet' as a good example. But then you have 'The Black Dahlia' adaptation, which proves that theory wrong. But I generally encourage folks to read a book first to get the images in your head, and form your own film version."
"A film adaptation that requires you to have read its source material is a failure — see 'Hobbit, The: Extraordinary Journey, An,' or better yet, don't. Book-to-film comparisons are often interesting, but that's a different beast from making a critical assessment of a film on its own merits. Often I've gone back to a book after admiring the film that was derived from it — James Ellroy's 'L.A. Confidential' and Nick Hornby's 'High Fidelity' are examples that spring immediately to mind — but I don't feel any responsibility to read a novel before reviewing its film version. I'm more likely to read the book first if it's a decades-or-centuries-old classic than if it's a contemporary book, if only to try to determine what has made the story resonate for so long."
"Interesting question. To be entirely honest I'm too disorganized a person to have anything resembling a system with respect to this issue. On general principle, it kind of doesn't matter, since the book and the movie are, to my mind, entirely discrete objects. So as a critic all I'm concerned about is whether a movie succeeds on its own terms. With particularly iconic or notorious books this can be a more pronounced problem. I think my attachment to the literary original of 'Lolita' certainly contributes to my perception of it as Kubrick's weakest film. My reservations concerning 'Killing Them Softly' weren't all that strident, but they were based in the irrefutable fact that Andrew Dominik would have done well to have stuck even closer to George V. Higgins' novel than he had. In the same genre, I feel almost certain that I'm gonna be frustrated by the Jason-Statham-starring 'Parker.' Donald Westlake/Richard Stark's books in that series are practically perfect for cinematic transposition, and yet… oh well, doesn't matter, is my point. The books are still the books. Whether I've read them or not could be my loss as a reader, but in terms of looking at the movie they shouldn't really enter into the equation. I did not hate 'Cloud Atlas' but seeing it was a sufficient experience that I have very little inclination to look into the book, which I had intended to read, yes, before I saw the movie. Back to that thing about not being sufficiently organized."
"I'm staunchly in the 'avoid the book' camp. As a critic, inevitably, you'll end up comparing the film to the book as you watch — which could be fruitful territory to explore but in my mind doesn't give the book a fair chance to work on you as a piece of art/entertainment. It's virtually impossible a film will contain more than the book, so enjoy the film first and see what the book 'adds' rather than what the movie subtracts."
"In the case of 'Mystic River,' I read the book first. In the case of 'No Country for Old Men,' I saw the movie first. I guess it comes down to how excited I am by the prospect of a certain filmmakers' new work. Or maybe I'm an illiterate. Either way, Dennis Lehane is a good writer."
"Since we're all friends here I'll be honest: I very rarely visit a novel once I have seen the film or vice versa. It's not out of laziness really (well maybe a little laziness), but more out of a sense of the narrative version of the uncanny valley. The first method of delivery of a story tends to stick with me, causing the secondary method to seem similar, but slightly different and strange. Different and strange enough to cause me to feel a little uncomfortable. The only exception to this that I can think of is 'The Lord of the Rings' films and books. That is the only time I can say I enjoyed both properties nearly equally. There it is, my neuroses all laid out in survey form."
"Once I hear a movie is being made, I usually avoid the book because they tend to get mixed up in my mind if I read and watch too close together."
"I've seen great films based on great books, bad films based on bad books, great films based on bad books, and bad films based on great books. I've seen films that struggle due to straying too far from the source material, I've seen films that struggle from staying too faithful to the source material. I've seen film adaptations in which the best scenes weren't anywhere to be found in the book. Great art should stand on its own, period. I would only read a book first if I'm choosing to write specifically about the story's adaptation from book to cinema. Otherwise, I like as a critic and a general moviegoer to judge a film's storytelling on its own merits."
"I very rarely will read the book, both as a factor of just not reading very much fiction combined with a desire to approach the work on its own terms. In fact, I often find getting through the book version quite a chore even if read after seeing the film — I couldn't get through McCarthy's 'No Country For Old Men,' finding all the subtle changes that the Coens made far more satisfying than anything I was reading. Similarly, I don't read scripts ahead of time, and in the best case scenario avoid all summaries or even trailers. I love to experience a work as fresh as possible, and some of my most extraordinary filmgoing experiences have been from this positions of being pleasantly surprised from the first frame. Whether or not I see the original film before a remake is a harder, case-by-case decision, one I'll leave to another Criticwire survey."
"It's never made a huge difference to me one way or another. If I know a film is coming of a book that I already wanted to read, then I'll make an effort to read the book first. Mostly, though, the film's the film. Typically movies based on books are either different enough to be taken on their own terms or similar enough to have the same strengths and weaknesses."
"Honestly, for me it depends on the book being adapted into a movie. I didn't go out of my way to catch up with Dan Brown's 'The Da Vinci Code' before seeing Ron Howard's film adaptation of it, and I don't really feel like I missed out (if anything, the revelations about Ian McKellen's character late in the film probably worked better for me because, unlike the many who had already read 'The Da Vinci Code,' I had no idea about them going in). However, when it comes to film adaptations of 'classic' works of literature — like, say, 'Anna Karenina' and 'Wuthering Heights' — I do feel a need to be at least somewhat familiar with the source material going into it, if only because of their reputation. Of course, whether such a familiarity necessarily enhances a film adaptation or not — well, some films try to be faithful to literary source material, while others not only flagrantly depart from the text but play off our knowledge of it. It all depends on the film, basically."
"I don’t mind reading the book if the movie’s release is at least a year or two away. If I hear about a filmmaker or studio contemplating adapting a novel, I will probably pick it up before production even begins. I really don’t like having the book fresh in my mind when I see the film. Otherwise I can’t avoid nitpicking it to death and it gets in the way of me enjoying the film for what it is."
"I’m actually fine both ways. I don’t go out of my way to read a book before I watch a film adaptation of it, but on the other hand I don’t avoid it at all costs either. I try to think of the film as a work in its own, not bothering too much about whether it’s faithful or not to its origins. Of course I fail at it sometimes, especially if it’s an adaptation of a book that I love deeply and that has made a very strong impression on me. My experience is that the version of the work that I encounter first — be it the film or the novel — is what I’ll end up loving most."
"I make it a point whenever possible to avoid reading the book when I know there's a forthcoming movie version, because I think the movie has to exist on its own, independent of the source material. (Odds are also good that, among readers of the review, more of them won't have read the book as well.) When it's a book I know, then I'll talk about the film's specific strengths and weaknesses as an adaptation, but all things being equal, I'd rather avoid the book the same way I'd avoid spoilers or trailers or leaked screenplays. Tabula rasa, for me, is always the ideal."
"I've gone a lot of different ways on this and there have been many examples where reading the book before seeing the movie spoiled the experience of enjoying the movie. For example, 'The Silence of the Lambs.' I really liked that book a lot and when I saw the movie right after finishing it, I was disappointed because it didn't live up to what I had read. Yes, you read that right. I was disappointed with 'The Silence of the Lambs,' but that was only the first time I saw it. The movie's grown on me the more distance I had from the book. On the other hand, I really wasn't into 'Hannibal' as a book and it took me over a year to finish reading it. By comparison, the film by Ridley Scott was a lot more exciting and I liked it better. Then we get to something like 'Nick and Norah's Infinite Playlist' which I read before seeing the movie and that book was way better than the movie. So going by these examples, I've sort of learned my lesson about reading and falling in love with books before seeing the movies. Now I'll read most of a book but not finish it until after I see the movie so it leaves something to enjoy. This is how I did 'Cloud Atlas' and 'Jack Reacher' (based on the novel 'One Shot') and for the most part, this gave me the best of both worlds but also allowed me to enjoy how the movie ends without having already read it in the book. Does that make sense? Probably not. But whatever."
"In the past, I've been one to read or have read plenty of books ahead of time before seeing their film adaptations, both by choice or by some sort of duty to put in the research to know exactly what I'm getting myself into ahead of time — after all, there is going to be a segment of your readership that has read the book already, too, and, as fans, might want some perspective on if the movie holds up to what they liked about the book to begin with. However, I think I'm starting to veer in the direction of avoiding the book, if possible, before seeing and ultimately reviewing a film adaptation, because, in many cases, it just ruins your experience with the movie. Let's face it: as hard as they try, they're just not going to be able to make the book exactly (with the exception of 'The Perks of Being A Wallflower' which came about as close as I've ever seen, thanks to the author being the one behind the creative decisions of the film). And, while we all go into films with our own baggage to begin with, this adds an extra layer, because it sets us up for the inherent comparisons between page and screen that the film can never win. There are going to be changes for time purposes or cinematic effect that fans of the book aren't going to like, and, if you enjoyed the book, you'll find yourself focusing on a lot of those alterations that may make for a weaker story — not necessarily a weaker film, but, compared to the book, a lesser experience. Therefore, if you're going in looking at a picture as just that — a movie — you're probably better off never cracking open its source material's cover."
"If it's a book I haven't read, I don't read it before seeing the movie (unless, maybe, it's something I wanted to read anyway). The only exception is when the movie is inspired by a short story, since it's revealing to see how the filmmakers interpret and expand on the source (and it's not time-intensive to do so). I do a little research on the book if it feels necessary or worthwhile, but it's really apples and oranges — unless your piece is specifically focused on adaptation."
"For me, there's no magic formula. If I've read the book or have never even heard of it, I remind myself that they're two different works in two different media, each with its own unique set of challenges and attributes. I think reading a book first has rarely negatively impacted my enjoyment of a film, and adds an extra layer of understanding to see the decisions that were made in adapting the book. However, recently I've enjoyed going back to the source material after loving a new film. For example, I've read some John le Carré since I saw 'Tinker Tailor Soldier Spy,' and that film only grows in my estimation understanding all the complex le Carré mythology that's peppered throughout that elliptical film."
"I used to attempt to read the book before seeing the movie. However I now prefer to avoid the book until I've seen and reviewed the film. I believe that film adaptations should stand on their own and have failed if they rely on the book to explain elements of its plot. Concurrently I believe a critic should be as untainted as possible by preconceptions when reviewing a film. Overall, I find the viewing experience more enjoyable and the reviews more apt when a film is experienced as such and not as an adaptation of a book. I find myself frequently annoyed by those who point out the differences between the film and book rather than discussing the film itself and its merits (or lack thereof) within its own medium. Films and books are two different kinds of art and an attempt should be made to approach them and discuss them as such."
"Easy. See the movie, then go read the book. To make something screen ready, film adaptations sometimes commit near criminal acts refining or reworking a well-received book. Unless you're Peter Jackson and have the studio's patience for 10 hours of story you'll never get everything from the book on the screen. It's a necessary and sometimes unfortunate evil in the editing process. But it's not all bad because let's face it, not everything in a book is geared to or needs to be told cinematically. So to avoid the heartache in the theater it usually pays to see it onscreen first and then, if you like it, seek out the novel. I'd much rather say 'that wasn't in the movie' but have the book make more sense than say 'oh, they changed/omitted that' and be disappointed by the adaptation any day of the week. It's not a foolproof stance to take but it works most of the time."
"I prefer watching the film and then maybe checking out the book. In college, I had to read the books and then watch the films for my movie classes. I remember having to read books like 'The Shining' and 'War of the Worlds,' and then watching the films. I wasn't particularly fond of that. Nowadays, I prefer to just watch the movie and then maybe read the source. For example, I remember watching 'The Lord of the Rings' trilogy and then going back to read the books. Most recently, I've done this with the TV show 'Game of Thrones.'"
"Currently I’m way too busy and am a very, very slow reader, so it’s very rare that I am able to read the book before seeing the movie. Last time I could was with 'The Hunger Games,' because it’s so short and I read it on my honeymoon in between beach naps. I wish I could do it more often with more substantial works, especially nonfiction titles associated with docs. When I was young I read everything beforehand, including (and especially) novelizations. Now I can barely get through a magazine article sourced as the basis for a film. Any films based on haikus coming out soon?"
"I never avoid a book because there's a movie adaptation coming out, nor do I usually go out of my way to read something I haven't yet read. I say usually because when that first six-minute 'Cloud Atlas' trailer dropped, I went 'Oh, wow, I should read that book,' but that was only because I'd owned the book for eight years and never made it past the first twenty pages. And I read 'The Hunger Games' because it only took about a day and it helped me keep a straight face when those names were said out loud in the movie. But as far as reading the book first being an across-the-board preference, no. There's a lot of compartmentalization involved in watching a movie adaptation that deviates from the movie one imagines in one's head while reading, and sometimes it's easier to just watch the movie."
"Neither. I like for movies to surprise me, so I prefer to know as little as possible going in. If it happens that I've read the book before the movie is released, hopefully enough time has passed so that I will have forgotten nearly every aspect besides the basic outline (That's what happened with each 'Harry Potter' film and 'Life of Pi'). As for reading a book after seeing the film, unless the writing is radically different (i.e.'The Prestige') or in the super rare case where I like the film so much that I simply have to experience it on the page, I'd rather just watch the movie again. Otherwise, I'm going through the motions of a story I already know when I could be reading a different book or watching another movie."
The Best Movie Currently In Theaters on January 7th, 2013: