Cassel just had one of the shittiest first halves ever.

[chiefzilla1501]

Originally Posted by keg in kc

You aren't the only person attacking the Cassel Challenge that way. Sorry if you felt that you were somehow being pointed-out.

Nice job, though, tossing names around when you don't have the brain-power to discuss like an adult.

Sorry, given that I'm the only one in here arguing the side, I thought you were referring to me.

It does surprise me that there are people that will look at today's game and actually think Cassel is any kind of an answer. Can't argue with that. I just think on the flip side, people will exaggerate to get their way. A lot of today was also on the receivers.

[keg in kc]

Originally Posted by chiefzilla1501

Sorry, given that I'm the only one in here arguing the side, I thought you were referring to me.

I don't generally do that. No worries, though.

It does surprise me that there are people that will look at today's game and actually think Cassel is any kind of an answer. Can't argue with that. I just think on the flip side, people will exaggerate to get their way. A lot of today was also on the receivers.

I think that's a very arguable point. I can think of 3 or 4 instances off the top of my head where he simply missed wide open receivers on what would have been key plays, and at least one of them would have been a TD (Charles in the first half). Unfortunately he's been making that kind of drive-killing play all year long. He's jekyll and hyde; plays like crap for 73:30 and then looks like a QB for 60 seconds today, or over the season plays like crap for 3 or 4 weeks, looks passable for a week or two, and then back in the crapper today.

He also made some poor plays that don't appear in the stat book, like taking a sack instead of throwing it away. He was lucky Stroud didn't knock him out of the game.

[chiefzilla1501]

Originally Posted by keg in kc

I don't generally do that. No worries, though.I think that's a very arguable point. I can think of 3 or 4 instances off the top of my head where he simply missed wide open receivers on what would have been key plays, and at least one of them would have been a TD (Charles in the first half). Unfortunately he's been making that kind of drive-killing play all year long. He's jekyll and hyde; plays like crap for 73:30 and then looks like a QB for 60 seconds today, or over the season plays like crap for 3 or 4 weeks, looks passable for a week or two, and then back in the crapper today.

He also made some poor plays that don't appear in the stat book, like taking a sack instead of throwing it away.

I don't agree with the Charles example. To me, that was a play where McCluster was really missed because he's more of a natural receiver. That looked to me to be more of a cross-up. And today, holding onto the ball too long was surprising--I haven't seen that from him in several games. I'll rewatch the game, as I'm curious to see if he should have actually gotten rid of the ball faster and I'm also curious how many of those were coverage sacks vs. just not seeing the open guy.

But yeah, all in all, missed a few passes he has to hit and has been much less effective in key moments (though, he was terrific in the Chiefs' final drive). I thought he took a few small steps forward against Houston and Jax then took a step back today. Which is bad, because he has to take a lot of giant LEAPS to be keepable.