Since this writer can't seem to understand that a spoiler alert goes BEFORE the spoiler, I'm just going to have to regard his byline as a spoiler alert and avoid reading anything beyond that.

No, I understand. It was on purpose.

"No, I understand. It was on purpose." I wish I'd seen that this was posted by the same writer. Otherwise I would have avoided such idiocy.

If you're going to review anything, you'd better understand this: You do not spoil. Not even if you don't like the film or the book or anything. The arrogance of spoiling is beyond comprehension, shows a lack of respect for the reader as well as for the film, and negates any valid observation you might possibly hope to make.

Hey dog, the whole point was to show a lack of respect to "Knights of Badassdom".

If you were really going to watch that and the spoiler in anyway "ruined" the movie for you, then I'm pretty sure this isn't the first time your film preferences have been disrespected.

i dunno, this review actually makes me want to see it now.

Exactly, its actually a pretty good film.

"Exactly, it's actually a pretty good film." This illustrates my point. Whether or not you like a film is subjective. If you don't respect the film, okay, but spoiling shows disrespect for the reader who may have a very different opinion.

There were reviewers in 1980 who hated the entire 'Star Wars' phenomenon, as I recall. That didn't entitle them to reveal to readers that Darth Vader was Luke's father. (Whoops! Spoiler alert! Too late!)

Robert, keep in mind that the spoiler in question here is that a dude fights a dragon. That's it.