My current reaction to a certain news item

There’s a thing that might be happening today, or it might not, and absent confirmation by the person who can confirm whether the hoped-for thing is in fact happening today, I will keep my reaction noncommittal. Moreover, everyone acting as if the thing that might be happening today actually is happening today would do well to listen to the wisdom of Mr. Toby Ziegler in this West Wing clip.

Or, failing that, Professor Jones’s wisdom from this scene in Indiana Jones and the Last Crusade:

INDY: Well? We made it!

PROFESSOR JONES: When we’re airborne, with Germany behind us, then I’ll share that sentiment.

Indeed.

Confirmation. I need it!

 

Share This Post

The problem with the playoffs is only one team gets a happy ending.

I haven’t written about football in this space (well, not this space, but you know what I mean) in years. I stopped watching football regularly more than ten years ago, and now I only watch if I happen to be someplace where it’s already on someone else’s teevee. But one would have to live under a rock to not know that a recent renaissance has taken place for the Buffalo Bills, after a long seventeen-year-long stretch of never making the playoffs and often being downright bad.

I’m not going to do a deep dive of any sort into yesterday’s playoff loss, a 42-36 defeat by the Kansas City Chiefs. You can find that sort of thing elsewhere–especially analyses of the self-inflicted wounds that were the special teams and defensive playcalling in the last 13 seconds of regulation time, when the Bills–owning a three point lead and just that long away from advancing–instead gave up a field goal to force overtime, and then a touchdown in OT to lose. What a sequence.

(I did not watch the game, by the way. I follow games online at times, seeing social media reactions and checking the box score in-progress. Why not? Sports got along just fine with most fans not seeing the games on teevee for decades.)

I will note, though, that the NFL’s overtime rules continue to be absolutely insane. It is inexplicable that they continue with overtime that makes it possible for a team to win while the losing team never so much as touches the ball. This defies all reasoning, and no other sport does it that way. Basketball and hockey have extra periods, and baseball just tacks on additional innings as needed, so the home team always gets one last at bat. Not so the NFL, which has decided that if the first team with the ball scores a touchdown, the game ends. But the game does not end if the first team only scores a field goal. This ridiculous kludge of a rule was what the NFL did after another notorious playoff game, one involving the San Diego Chargers and the Indianapolis Colts, if I recall correctly. The Chargers got the ball and won immediately on a field goal, while Peyton Manning, then one of the game’s biggest stars, watched in sullen silence before heading for the locker room.

The same thing happened last night: Buffalo’s Josh Allen, one of the games brightest stars these days, never got a chance. You can’t tell me that the NFL wants it this way. There’s a reason they scheduled Bills-Chiefs as the late game on Sunday of Divisional Playoff Weekend: because that’s the game most people would want to see. And yet, it ended in a lame coronation because of the league’s stupid overtime rule.

The way to fix this is, for me, fairly obvious: add ten minute periods as needed, and just keep playing until time expires and there’s a winner. I’d keep play moving by awarding no timeouts to either team, and I would eliminate the coin toss by simply positing that the visiting team gets the ball first. (Oh, and I’d also eliminate the opening coin toss as well. In baseball, the home team always bats in the bottom of the inning, and I’d do likewise in football: the visiting team receives the opening kickoff in the 1st, and the home team receives in the 3rd.)

A game’s stars need to play. The NFL’s current system allows for a possibility of the game’s stars being spectators to their own defeats. This is just absurd.

Also, on Josh Allen: my God, can you imagine having a quarterback put up the postseason that guy did, and still falling short? It’s astonishing, and it reminds me of a scene from Star Trek:

What’s happening here is that the Enterprise is participating in some simulated war games, pitting Picard against Commander Riker. But as they get underway, Data has just lost a strategy game like chess to some guy, leading him to conclude that he must be malfunctioning. Picard finally has to go tell him that no, he’s not malfunctioning, he just got beat.

Anyway.

That’s about all I have to say about last night’s game. It’s time for the offseason. The draft is in three months. Training camp’s in six. Better luck next year, Bills.

 

Share This Post

Live and Let Rank: The Official and Correct Ranking of the James Bond Movies, part 2

Continuing my Official And Correct Ranking of the James Bond films! This time we will go from Number 20 to Number 16. Our first entry contained the one Bond film I outright dislike, followed by several that just don’t do a whole lot for me and which are almost never my flick of choice when I decide I want to watch a Bond movie. With this list, we start getting into “Not my favorite, but watchable and sometimes I’ll turn it on for fun” territory.

Here’s the ranking thus far:

26. LIVE AND LET DIE

25. DIE ANOTHER DAY

24. THE SPY WHO LOVED ME

23. GOLDFINGER

22. DIAMONDS ARE FOREVER

21. A VIEW TO A KILL

And now, we move on!

20. TOMORROW NEVER DIES

Some years ago a blogger named Snell had a James Bond blog that he updated for major Bond events (new films, news of new films, that sort of thing). Sadly Snell died about a year ago, so he never got to see No Time To Die, but he did cite me in his review of Tomorrow Never Dies, when I had previously referred to that movie as “a film I like as an action movie, but not so much as a Bond movie.” I stand by this assessment to this day. Tomorrow Never Dies would, I think, be frankly better if it was simply redone for some other action hero. It took me a long time to really figure out why I always have such a weird relationship with this movie, and I finally figured it out: TND is the least subtle Bond movie ever. This movie doesn’t have a single ounce of subtlety in it. And that’s my problem with it.

You may be thinking, “Bond? Subtle?” Well, yes! The Bond series won’t ever be in the Subtlety Hall of Fame, but these movies do tend to deploy subtlety in enough doses to be effective. TND, though, is just blunt-force trauma from start to finish. The precredit sequence is a thrilling mini-action movie on its own, yes–and it ends with Bond apparently being able to include “flying a modern jet fighter with more skill than trained pilots” in his skill set. Bond can apparently use the touch-screen controls on his 90s-era phone to drive his new car with as much precision as he’s ever driven anything else. This gives us another very nice action sequence (the action in this movie is some of the best-filmed action in any Bond movie), but again, a disconnect: He can drive like this with a remote control he’s never touched? And he’s laughing with delight as he does so, minutes after he saw a former lover murdered?

On that last point: my general take on the Brosnan films is that they are full of great ideas that are executed poorly, for one reason or another. This is why a lot of ideas from Brosnan’s films showed up again in the Daniel Craig run: it’s as if Neal Purvis and Robert Wade, writers of Brosnan’s last two movies, were set free by the jettisoning of the Bond Formula that came with the series reboot, and thus were able to put their ideas to better use. Note that Purvis and Wade did not write TND, so they’re blameless here, but TND has two great ideas, and only one is done well. The one they nail is the media mogul villain who is manipulating events for his own profit. Yes, we’ve seen this in You Only Live Twice and The Spy Who Loved Me and Moonraker and A View To A Kill, but Jonathan Pryce’s Elliot Carver is a particularly nasty and believable piece of work, coming as he does in the late 90s, when we were just starting to become aware of giant media conglomerates starting to consolidate their power.

The other great idea in TND, though? The one handled badly? That’s Paris Carver, the Teri Hatcher character.

Think about James Bond, and all the ex-girlfriends he has all over the world! Think how many times he’s had the break-up speech. Yes, some of those were undoubtedly mutual; I’m sure Octopussy was fine with it, because she was a mature woman with her own doings in life. Others, though, were probably less thrilled to get dumped by Bond. And here comes TND, which puts Bond in the position of having to contact one of his former lovers from an old adventure of his! That is a great idea! I loved this idea. The previous Brosnan flick, GoldenEye, had Bond squaring off against a former Double-O, and now this one has him with a former lover. But the character is wasted, just becoming another in the long line of Bond Girls Who Die At The End Of Act One. Bond and Paris have a conversation (“Tell me, James, do you still sleep with a gun under your pillow?”) that is immediately eavesdropped on by our boy Elliot, who is instantly aware of his wife’s possible faulty loyalty. So we know her fate barely a minute after she’s introduced onscreen.

Lack of subtlety? How about the film’s briefing scene? It takes place not in M’s office but in a car speeding to the airport, and it serves less as a briefing and more as a series of sexual puns using the word “pump” (“Contact Mrs. Carver, your former lover, and pump her for information. You may have to do a lot of pumping. Pump away, 007.”) And the Michelle Yeoh character? Yeoh is terrific! I totally believe that she’s pretty much Bond’s equal, though once again we get a Female Bond who ends up in a pickle while Bond does the world-saving all by himself. We don’t get much about her as a character, unfortunately–the movie has to spend its first act on Paris Carver, so that we feel bad when she’s killed, and by this time the plot is whisking along so there’s no more time for any character stuff, so Wai Lin is shorted in the character department. She and Brosnan do have chemistry, but so did Brosnan and Hatcher, so this movie wastes two potentially good female characters.

Joe Don Baker’s not-Felix Leiter character? I liked him a lot and I wish he’d been around for more of these. Alas.

Oh, and TND saw the arrival of new Bond composer David Arnold, who did terrific work here, weaving in snatches of references to older themes and alluding to John Barry’s style while doing his own thing. The title song by Sheryl Crow isn’t a favorite of mine, while the kd lang song that closes out the film is a terrific ballad in Bond tradition. Arnold’s score actually incorporates the kd lang song’s tune, so I assume that was meant to be the title song before someone higher up the food chain at Eon Productions or MGM mandated using Crow. Anyway….

19. QUANTUM OF SOLACE

OK, after the big word-dump on TND, I’ll try to rein it in a bit on Quantum. We’ll start with the Rule of Bondian Time, a law I’m just now positing: Beware a Bond film that ends in under two hours.

I’m serious. I’ve just looked it up, and there are, to this writing, five Bond movies with run times less than two hours, and four of those are in the bottom half of my rankings. (One of them does make it into my Top Five, but every rule has an exception, no?) Bond stories need time to unfold. They tend to be fairly complex, plot-wise, and each one needs to establish a new set of characters. When these movies get short, it’s almost always to the detriment of story, character, or both. Can Bond movies be too long? I suppose, though I tend to default to Roger Ebert’s formulation: “No good movie is too long, and no bad movie is short enough.”

As of this writing, Quantum of Solace is the shortest Bond movie ever made, at 1 hour, 46 minutes. This comes after Casino Royale‘s 2 hours, 24 minutes, so Quantum feels like a bit of whiplash, especially when Quantum does a first for a Bond movie: it starts literally minutes after the last one ended. I’ve come to think that this may have been a mistaken choice in terms of narrative, because Quantum asks us to (a) follow Bond’s relentless quest for the nefarious organization behind the scheme that ended up costing Bond the first great love of his life, Vesper Lynd, and (b) acknowledge Bond’s grief at the disastrous end of his first true love affair. Quantum ends up being slightly more convincing on the former score and less so on the latter, partly because it compresses all of this into basically a few days of story time, and because it passes by so relentlessly quickly that none of the story elements really come together. Shame, that.

Quantum was partially hampered by a writer’s strike that sent the movie into production before the script was really ready, and stories abound of Daniel Craig spending his time not in front of the camera hastily scrawling script pages off to the side. Also, the movie looks strange for a Bond movie: washed out and even garish at times, and the action sequences are famously terrible, with quick-cut speed substituting for establishing shots so at times we’re not even sure what the hell even happened. Quantum is worth watching, but it’s ultimately a frustrating misfire.

David Arnold returned to score, but I have no real opinion of his work here. I should give the album another listen at some point. The song is not my cup of tea. I’ll leave it there.

18. THUNDERBALL

After talking about two movies that whip along and give their stories too little breathing room, here’s one that gives its story too much breathing room. There’s a lot of good stuff in Thunderball, but it all comes in the second act; the first act is 40 minutes or so of plot set-up, and the last act feels like 40 minutes of slow-motion underwater ballet “action”.

Thunderball is that odd duck of a film, the one that made the James Bond films a legal mess for decades, owing to some literary partnership between Ian Fleming and Kevin McCrory. I won’t go into that here, but there are legal reasons why Blofeld and SPECTRE disappeared completely from the James Bond mythos after Diamonds are Forever, and why McCrory was able to make his very own Bond movie 18 years later, called Never Say Never Again and starring Sean Connery, featuring the exact same story as this one.

The villain’s plot is very straightforward here, and there’s something kind of refreshing about the Bond films where you get the villain’s scheme in the first act. SPECTRE steals two atomic bombs and threatens to detonate them someplace unless they get paid a pile of money. That’s it. Again, it’s refreshing! It sets the movie up as a race against time. How odd, then, that a movie whose plot is a race against time has some of the worst pacing of any Bond movie.

The first act, as noted, is all set-up: Bond is at a health clinic, where some other guy is recovering from surgery to be made to look like an RAF officer. Bond notices weird shit going on but isn’t sure what to make of any of it, but he somehow angers some dude to the point of tit-for-tat injurious pranks, and there’s a very uncomfortable “seduction” scene that is frankly rape. Meanwhile the surgery guy turns out to be a SPECTRE guy who is standing in for an RAF guy on a plane that’s carrying two atomic bombs. He takes over, poisons, the crew, and crashes the plane in a specific spot in the Bahamas so the main villain, a SPECTRE guy named Largo, can steal the bombs. And he kills the RAF officer body double, who has already been killed, and who is the brother of Largo’s girlfriend.

Yes, Thunderball gives us all that convolution in the first act, before we ever get to Bond getting briefed by M.

Once we finally get Bond to the Bahamas (sent there instead of Canada because Bond just happened to find the RAF guy’s dead body at the health clinic even though the RAF guy was seen boarding–that’s our body double!), Thunderball gets more interesting, though it remains pretty convoluted. Bond pisses off Largo by beating him at cards, and then Bond seduces Largo’s assassin, and then Bond seduces Domino once he figures out that Largo has the bombs. Finally we get to our climax, which as noted, is a really long underwater chase-and-battle sequence, followed by ships, followed finally by a fight on the bridge of an out-of-control speedboat.

Thunderball is a gorgeous film to look at, and there are some iconic moments in it. But it just feels slow and bloated every time I watch it, and I also think this is when Sean Connery started seeming a bit less invested in the part. John Barry’s score is outstanding, and of course there’s that gonzo song crooned by Tom Jones, with its ridiculous lyrics (“And he strikes…like Thunderball!”) and his apparent death from self-inflicted asphyxiation on that last high note.

17. YOU ONLY LIVE TWICE

I loved You Only Live Twice as a kid, but I’ve liked it less and less as time has gone on. Another simple villain plot, this time involving outer space: SPECTRE is swiping American, and later Russian, space capsules right out of the sky, hoping to trigger a nuclear war between the US and the Soviet Union, apparently at the behest of China. The British, seeing some weak indication that maybe the kidnapped ships came down somewhere near Japan, send James Bond to check it out.

YOLT is another example of an under-two-hour Bond film not being as good as it should be, but in this case, I don’t think the issue is pacing. The issue here is that the 1960s-era sexism and racism is just impossible to ignore. This movie has so many moments of pure cringe that it casts a pall over the entire thing (“In Japan, men always come first and women come second!” Bond is told, to which he responds, “I just may retire here!”). Also this movie makes a very odd narrative choice regarding the “Bond girl”: it keeps the first one around almost to Act Three, and then she’s killed off. So we actually have some investment in her character, and the one that’s brought in minutes later to finish out the movie is almost literally a stand-in. Her name is “Kissy Suzuki”, which we only know because the credits tell us this.

Donald Pleasance is on board as Blofeld, and this time we finally get to see his face, which has an odd scar on his right eye. I’ve never been able to decide if I like Pleasance’s take on Blofeld or if I hate it. He does seem creepy and evil at times, but at others he seems almost whiny. He’s weird. There’s a beautiful woman assassin who is way less interesting than Thunderball‘s Fiona (one of the series’s best femme fatales), and there are many moments that just defy disbelief (how are they watching video footage of the helicopter seizing the car of goons? And is dropping cars full of goons into the ocean to drown really a thing?).

YOLT is another of the “Under Two Hours” Bond films that I tend to rank lowly, but of it’s one of those that I don’t think really suffers much for its relatively short running time. All the story is there. I just find the movie more and more uncomfortable to watch as the years go by. (This is also not surprising given that the film was scripted by Roald Dahl, who in addition to being a wonderful writer, was a wildly problematic guy.)

On the plus side, YOLT is quite beautiful to look at! There are a lot of very nice Japanese vistas, and there’s a distinctive early shot where some American and Russian officials are meeting to discuss the alarming events the kick the movie into motion. I particularly love a particular fight scene on the Kobe docks, when Bond is running across the roof of a warehouse, evading goons as he goes. This is actually an aerial shot, which is unique even for this series. There are some painful special effects along the way (artifacts of the time, but still, yeesh–did they have to do rear projection with Connery in a boat? Could they really not get that shot for real?), and for a short movie, the pacing isn’t what damages it. I even like the song, sung by Nancy Sinatra, with its lyrical hook.

16. SPECTRE

Ohhh, poor Spectre. This movie has taken quite a beating since it came out, and not all of it has been undeserved. It really is a wildly convoluted movie, story-wise, and it probably does go too far in trying to suddenly tie the previous three Craig films into a single story entity. Personally, I would have been fine with bringing Casino Royale and Quantum of Solace into the “single narrative” fold, but Skyfall was a bit too much for me, as that movie really stands on its own in a singular way. But other aspects of Spectre that have led most fans to pushing this one farther down than I do? I’m fine with them. Once again, we see how wildly divergent opinions among die-hard Bond fans can be!

So, what of Spectre? Well…I really do like it quite a bit. In fact, writing this I’m wondering if I should bump it up even higher on my rankings…but maybe not. It feels a bit like an attempt to recreate the magic and mood of Skyfall, likely because the same director returned for it (despite his previously having said that he was a “one and done” Bond director). A lot of the mood, the film’s visual look, the framing of shots–a whole lot of Spectre is obviously reflective of Skyfall, which is OK for the most part. And some of what happens in this movie is downright amazing! Of course, the opening tracking shot in Mexico City; and I love the Alps setting and the train through the desert.

Storywise is where things get a bit dicier for Spectre, though again, I like this movie more than most. After Skyfall, the legal quagmire that had dogged the Bond franchise for decades finally got resolved, so at long last, Eon Productions was once again allowed to use Blofeld and SPECTRE. I’ve always wondered if they had a script in progress when this legal gift came in the mail, and rather than wait a movie or two to get back to Bond’s version of Moriarty, they grafted Blofeld and SPECTRE (renamed in the new film to no longer be an acronym) onto their existing story. There’s a feeling of disjoint here between the schemes of Blofeld and those of C (Andrew Scott), the new head of MI6 who is developing a super-duper rights-violating surveillance system. Blofeld is behind all of it, but we don’t really get that much of a sense of it, do we?

And then there’s the whole business of Blofeld being “the author of Bond’s pain”. Most fans seem to take this as meaning Blofeld has been specifically plotting against James Bond for his entire life, inserting himself into every single bad thing that’s ever happened to him, but I don’t take it that way. I think he’s rather run his own life and his own schemes, and when things have happened in such a way that James Bond has been on his radar, he’s acted to screw Bond as hard as he can. That I can see, and that I have no problem with, in all honesty.

People also hate the idea that Blofeld was actually Bond’s foster-brother way back when, and honestly, I don’t hate this, either. Not in this context. There’s a theme running through all of Daniel Craig’s Bond films, distinct from any other actor’s run, of Bond confronting the sins of the past, whether it be Vesper Lynd’s past, M’s past, or, eventually, his own. Throughout these movies Bond is constantly having to deal with the fallout from other peoples’ various bargains with the devil, so I honestly have no problem at all with all of this eventually boiling down to what his parents did, or what happened in his youth.

What does bother me in Spectre is that a lot of this whips past, sometimes in the middle of actual action sequences or very quick conversations, so the film can’t actually set any of this stuff in the context where I think it makes sense. Bond calls Q at one point and says something like, “Look up Franz Oberhauser!” The moment is gone too quickly, so the script doesn’t really give us any reason why Bond is asking about some guy with a German-sounding name. Likewise, the opening Mexico City scene: Great scene, but apparently it was Bond acting on his own. When we find out why he went there to kill that one guy, it turns out that it’s M, the old M, Judi Dench’s M, telling Bond via posthumous video: “Find this guy, kill him, and then attend his funeral.” Why? She doesn’t say. How did she have this information, and what was she doing with it? She doesn’t say. This is what bothers me about Spectre: not the what of what happens, but the fact that an awful lot of it doesn’t seem to rise naturally in story terms. Things happen in this movie because…this is where something happens in this movie.

Take the fight on the train. That’s a hell of a fight! One of the best fight sequences in Bond movie history, if I’m being honest! But…it happens hours after they board, so what was Hinx waiting for? And don’t all those other people on the train notice something like a couple of secret-agent types destroying almost three entire train cars’ worth of stuff? How did Bond win that fight and then get allowed to stay on the train until their stop? That whole sequence is strange…but it’s there because “this is where something happens in this movie.”

Spectre has a nice score by Thomas Newman (following up his work on Skyfall), and while the song–“Writing’s On the Wall” by Sam Smith–seems to be fairly unpopular with fans, I actually quite liked it.

Next time: Numbers 15 through 11! We enter the top half of my ranking! Huzzah!! Taking stock, here’s how many films we have left, by Bond actor:

  • Connery: 3
  • Lazenby: 1
  • Moore: 4
  • Dalton: 2
  • Brosnan: 2
  • Craig: 3

Tune in!

Share This Post

Our annual Festival?

Thanksgiving is over, and now comes Christmas!

Every year I hear a lot of complaint that Thanksgiving is a thing that gets lost in the shuffle between Halloween and Christmas, and that Thanksgiving should be its very own thing with no Christmas trappings of any kind allowed until Black Friday at the earliest. But to be honest, I don’t agree, and the reason why has to do with how we structure our year, how we see time, and how we mark the passage of days.

Human culture has always structured its years around annual events, like planting time, harvest time, full moons, solstices and equinoxes, and the like. These events formed the basis of the earliest liturgical calendars of our religions, and feasts and festivals would accrue around them. Perhaps the most famous of these long festivals these days is the month-long fasting celebrated by Islam as Ramadan. These types of celebratory events used to unfold over multiple days. The Olympic Games were a festival. So too, once, was Christmas: the song “The Twelve Days of Christmas” refers to Christmas not as a singular holiday but as a festival, one that took twelve days to unfold. Twelve days of celebration, of feasting, of prayer, of reflection.

Now, our American society seems on one hand to want to limit celebrations to a single unit of time, one holiday and only one at a time, but on the other hand open itself up to celebrations that take place over time. We seem to want, in other words, a singular holiday and a festival, but we don’t approach it this way, do we? No, we come to the Christmas “season” like a time for lots of demands on our time: there’s cooking and cleaning and shopping to be done, and there are parties and special church services and the Christmas play and yada yada yada. All of these could be seen as trappings of a festival, but since we try to limit our celebrations to one holiday, we more see these things as items to be checked off a to-do list, required preparatory motions to be endured before we can take our one day off to celebrate, feast, pray, and reflect before getting on with the appointed industry of our lives.

I think we need to recalibrate our approach to and expectation of Christmas. I think we need to see this entire time of year as a festival, and I think it’s fine to posit Thanksgiving as the beginning of this festival. It just doesn’t make sense to me to cordon off Thanksgiving as its very own thing, independent of and separated from Christmas. I’d rather have our great Christmas Festival begin with Thanksgiving, a great day of feasting, and then extend over the however-many-days-there-are between that at the 25th of December…and then extend it right to the 1st of January. Instead of getting upset every year that Thanksgiving is “eclipsed” by Christmas, let’s approach it in the same spirit, because really…shouldn’t we do that anyway? It seems to me the emotional fabric of both days is very similar, and the two days are close together.

So let’s have Santa and the turkey at the same table.

Share This Post

SNOW!!!

Feels like it took longer than usual this year, but it’s finally here!

SNOW!!!

I reserve the right to get sick of the stuff once my traditional cut-off date, St. Patrick’s Day, rolls around (though for some reasons to be revealed later, my tolerance for snow this year might actually be increased). But for right now, I am happy as a clam, because SNOW!!!

 

Share This Post

How to Anger the Twitter Gods

I’m in Hour Two of a twelve-hour long suspension from Twitter because I broke one of its rules. The suspension happened very quickly, so obviously I didn’t manage to render my thought in poetic enough fashion to not trigger Twitter’s content bots against violent content or something. I deleted the tweet, but the 12-hours are still imposed. Oh well!

Not that big a deal, and if you’re wondering what got under my skin, it was a series of things Green Bay Packers quarterback Aaron Rodgers said about his current COVID status and how mean the NFL is to not consider his essential-oils-and-homeopathic-bullshit regimen as “immunization” equivalent to being fully vaccinated. He started off with saying something like “I’m going to be done in by Woke People and by Cancel Culture.” Now, I’ve recently adopted the personal policy of filing such citations of “Wokeness” and “Cancel Culture” under the same category as when people claim to be “Politically Incorrect”: After that, I stop listening to whatever it is they’re saying.

But one bit of dumbassery Rodgers said did manage to actually tweak me. He was babbling about “his own research” and “his own immunization regimen” and a whole lot of crap, but then he was quoted as saying something about how “liberals hated vaccines when 45 was President but as soon as Biden took over they loved them”. This is so mastadonical in its rhetorical turd status that I couldn’t help myself, so I fired off a tweet expressing my hope that Mr. Rodgers tear his ACL as soon as he steps on the field next.

Yeah, not my best hour. Shouldn’t have said it. I grant that.

But it’s still complete bullshit.

I’m no expert on all the details, but my understanding is that Operation Warp Speed, the program spearheaded by the 45 administration to facilitate vaccine development, was pretty much a success. There’s a reason why all those vaccines were ready to go not long after Joe Biden’s inauguration. No one with half a brain seriously credits the Biden Administration with the entirety of the US vaccine response.

And there was a time when the right (and I assume now that Aaron Rodgers is one of those) believed the same thing. There was a brief time when they were really trying to push giving credit to 45 for the vaccines. Someone, I think it was Geraldo Rivera, said something like “Let’s call it the Trump Treatment!” The idea that the American left would be suddenly vaccine-hesitant if 45 had won re-election and everything else had been the same is a pleasant fiction, but there’s no doubt that if 45 had won a second term and everything else had been the same, FOX News and everyone else would be trumpeting the vaccines as one of the greatest humanitarian triumphs in history, all because of the greatness of President 45. We know this because they actually did start talking like this, before they collectively decided that no, the real victory lay in pulling back on their pro-vaccine talk, instead defending the honor of Ivermectin and amplifying anti-vaccine voices as much as they could (while privately making sure that each and every person working for FOX News is vaccinated).

In short, Aaron Rodgers is a deluded dope who has no idea what he’s talking about. But on Twitter, you can’t wish him a season-ending injury. OK. Message received, Twitter.

But this site right here is my site and I get to say whatever I want on my site, so: Hey, Aaron Rodgers! I hope you blow your knee out!

(Comments closed on this one.)

Share This Post

“I shall read you to the bitter end!” vowed the Reader….

An interesting discussion erupted over on Twitter the other day, occasioned by this tweet:

https://twitter.com/nakedvix/status/1448595705128529920

Almost exclusively the discussion hewed to one side of this argument: that it is, in fact, deeply silly to suggest that a reader is insulting an author by leaving a book unfinished, for whatever reason. One writer and book commenter and critic and reader after another came forth to insist that no, as a reader, you absolutely should stop reading books that for whatever reason aren’t clicking for you. You owe the author nothing, and there is utterly no insult to an author simply because one reader didn’t connect with a book.

In short, everyone piled on the writer of this tweet, and given the formulation of the position stated therein, that’s probably correct. I myself do not hesitate to leave books unfinished if I am not enjoying them.

However!

(There’s always a “however”, isn’t there?)

In this case, the writer behind the tweet above, Victoria Richards, is merely paraphrasing the headline above in the article she links in her tweet. Reading that piece, I found myself agreeing–at least a bit. The actual point the article’s author, Rupert Hawksley (a writer with whom I am unfamiliar), is a bit more nuanced.

A bit.

Yes, the headline reads “It’s an insult to authors to not finish each and every book you start,” but when we dig in we find something else:

Earlier this week, the novelist Mark Billingham caused a minor stir when he suggested that readers should throw a book “across the room angrily” if it hasn’t gripped them in the first 20 pages. Speaking at the Cheltenham Literature Festival, Billingham said that he gives up on about half of the books he starts because “life’s too short … There are so many great books out there.”

Plenty of others agree with him. Hilary Rose, writing in The Times, explained that she “bitterly regret[s] not heeding Billingham’s life lesson sooner”. Crime writer Linwood Barclay added: “Think of it this way. If the first three bites of your meal taste terrible, you don’t need to keep on eating, expecting it will get better.” Well, no, though I’d point out that if the starter was disappointing, you might still stick around for the main. Plenty of iffy prawn cocktails have been followed by an excellent steak.

Reading is, for the most part, a private pursuit; it’s unlikely many of us would seriously change our habits based on the advice of others. Whatever works for you, I suppose. Still, I have found the discussion this week dispiriting and, dare I say it, a bit childish. The idea that we read simply to be entertained – as an easy form of escapism – seems to underpin all the arguments for giving up on a book: “I couldn’t get into it”, “it didn’t grip me”, “too slow”. But entertainment, surely, isn’t the only reason why people read – or indeed why authors write.

Reading should challenge and confound us; it should take us into the minds and lives of those we don’t like or find hard to understand. This may not always be gripping but it is often rewarding. We owe it to writers to give them a full hearing before passing judgement – and finishing a book is the only way to do this. To give an author just 20 pages of your time is insulting.

That last bit is key: We owe it to writers to give them a full hearing before passing judgement–and finishing a book is the only way to do this. To give an author just 20 pages of your time is insulting.

Also of note is the way Hawksley starts: he is responding to someone who has said that a reader should fling a book angrily aside if they’re not enjoying it just twenty pages in. Now, there’s no link there to substantiate the quote, so it seems to me that Hawksley is framing a stronger-than-necessary response to an argument that is, the way he depicts it, also a bit strange.

All I can do here is offer my testimony as a reader myself. I stop reading books (what the kids today call “DNFing”, with DNF standing for “Did Not Finish”) probably around a quarter of the time. That is to say, I suspect that I DNF around a quarter of the books that I start. Why? Well, there are many reasons! There’s the “It didn’t grab me” thing, which is a thing, I have to admit. There might be other factors involved: I’ve had to DNF books that came due at the library before I could get all the way through. (This may, in fact, be the main reason I DNF stuff. Sometimes I’ll make a note that I was liking the book and check it out again; other times I won’t bother.) And sometimes there are other reasons for DNFing a book. I’ve had a few instances of starting a book just in time for the author to, well, show their ass on the Internet by saying something awful. I don’t like to do that, but I can’t really enjoy a book knowing that the author has just exposed themselves as a big jerk.

Here’s what I don’t do, though: I never pass judgment on a book that I did not finish. A cursory glance at my Goodreads account makes it look like I like all the books I read, but that’s not quite it: I won’t review a book I didn’t finish (I have a DNF shelf on Goodreads for my own record-keeping, and it has only seven titles on it), and I don’t finish what I’m not enjoying. This seems fair to me.

I also very rarely conclude that a book isn’t good. When I DNF a book for a reason involving the book itself, it’s because of that dreaded “it didn’t grab me”…but even so, I don’t read too much into that at all. I’m more likely to say “This wasn’t doing it for me right now, but maybe it will some other time.” And that is always possible. Many of my favorite books of all time are books that I couldn’t finish the first time I tried reading them. I see a DNF for this reason as not being a statement of any kind about the book, or me, or me and the book. It’s just “Meh, this isn’t what I feel like reading right now.”

That original author’s statement about flinging the book aside angrily if you’re not grabbed in 20 pages? Isn’t that a little weird? How can 20 pages possibly be enough to know if a book has “grabbed” you? And why be angry at a book that simply hasn’t engaged your emotions on this particular day? In fact, the books that make me angry might be the ones I’m more inclined to finish, for whatever bizarre reason. It doesn’t happen often, but I will note that I wish, from the vantage point of experience and time, that I had chucked The Fountainhead and Atlas Shrugged against the nearest wall. But even in those cases, I doubt I’d have done so a mere twenty pages in.

Ultimately I think readers and authors put way too much stock in a book’s need to “grab your attention”. The advice is constant: “You have to grab your reader! You have to command their attention from the first line! If they have the slightest reason to put your book aside, you’re done!” Sometimes you hear this stuff from editors and agents, but those are special cases: their jobs involve reading more stories or novels than any human can reasonably process in a week, so of course they’re going to reject books within a few pages, if that. But what of that? What does that mean? Again: merely that the book didn’t click with that person at that time.

So, in the end, I think the only real insult to an author comes when you judge a book harshly without having finished it. You should come to a book with the most open mind possible, but it is simply unreasonable to expect that in every single case a reader will be prepared to go where the author wants to take them. You never know until you try, I guess…but don’t worry about insulting the author. Especially if you bought their book, because then, well, they’ve already got your money.

Share This Post

Something for Thursday

I watched the Blue Origin flight yesterday, in which William Shatner joined three others in the very short up-and-back-again space shot yesterday in Jeff Bezos’s interestingly-shaped spacecraft. I have to admit to a certain amount of cynicism as I’ve watched the breathless reactions in recent years to the achievements of a tiny handful of ultra-wealthy white men who have apparently decided that the best thing to do with their vast sums of money, sums that it seems to me a sane society would make it impossible to accumulate in the first place, is to replicate things that the United States government did sixty years ago.

I don’t even mind, really, that this is the way it’s shaping up. The really ground-breaking stuff, the envelope-pushing stuff, needs to be done at the government level, because that’s still the level that can operate in the amounts of capital needed to do the experimental work. If the rich then want to test the waters that have already been explored, that’s great. And that’s what’s been happening…only with a sense of worship about what the Bezoses and the Elon Musks of the world have been accomplishing. I’ve even heard it suggested that maybe now we can just do without NASA entirely, get government out of the space game, and let “Private enterprise” or “the Free Market” or “capitalism” get about the work of really making space exploration happen.

As always, to this I say, “Bollocks.”

But…but!

On the other hand…a spaceship launched yesterday, and it blasted a capsule into space. Then the launching craft didn’t just tumble back to earth to be swallowed by the sea; it fired its thrusters again, extended four landing legs, and landed right where it started. Meanwhile the capsule completed its trajectory, entered space, arced back down, and parachuted back to earth.

The passengers (I trouble to call them “astronauts”, in all honesty) climbed out then. Three of them hugged and high-fived and cheered and hooted and hollered and sprayed each other with champagne. But the fourth? He, Mr. Shatner of Star Trek (and others) fame, stood off to one side, as if gathering his emotions. This flight had moved him deeply; you could see it in the way he stood. Then he started talking, and said, among other things:

“I mean, the little things, the weightlessness, and to see the blue color whip by and now you’re staring into blackness. That’s the thing. This covering of blue is this sheet, this blanket, this comforter of blue around that we have around us. We think ‘oh, that’s blue sky’ and suddenly you shoot through it all of a sudden, like you whip a sheet off you when you’re asleep, and you’re looking into blackness – into black ugliness. And you look down, there’s the blue down there, and the black up there, and there is Mother Earth and comfort and – is there death? Is that the way death is?”

Look, I can be as cynical as anyone about rich people and them treating space like it’s their playground and ignoring the problems of the world and the fact that they profit greatly on some pretty nasty labor practices. But…there’s still space! My heart will never not thrill to a rocket ship blasting away from Earth, or to space passengers disembarking their spacecraft after returning to Earth. And I will never not be moved to hear those returning to Earth talking about the planet’s blue blanket.

Great human achievements are never just so…but they are still great.

Oh yeah, this is supposed to have some music, isn’t it? It’s a Something for Thursday post. Here’s a suite from Bill Conti’s score to The Right Stuff.

https://www.youtube.com/watch?v=tCblQ_fnPpc

Share This Post