Looney ... The Morning After: Philadelphia
 

The Morning After: Philadelphia

By Josh Looney
Posted 5 hours ago
Chiefs show grit, but still not a win

http://www.chiefsplanet.com/assets/i...50_8_28_10.jpgMr. Kansas City himself called me shortly before kickoff last night. Bill Grigsby is the best. When it comes to re-living Chiefs history, there are few better sources than ‘Ole Grigs.
Anyway, he asked me if I had a Chiefs record book handy, which I did. Grigs wanted to test his Chiefs knowledge.

“Now correct me if I’m wrong,” Grigsby said. “But the first time that the Eagles and Chiefs played each other was in 1972, and the Eagles won that game 21-20.”

He was correct; and then, of course, went on to tell a story from that day in Chiefs history.

Grigsby’s tale involved the Chiefs being three-touchdown favorites against Philly. The Eagles were woefully bad that year, 0-5 when they visited Arrowhead (they’d finish 2-11). Unfortunately, for the Chiefs, there was a pre-game alarm as to what was about to come.

“I get out there and our United States flag that’s flying at the top of Arrowhead is upside down,” Grigsby explained. “(Former GM)Jack Steadman was running around like Catfish Hunter with a no-hitter in the ninth inning and the bases loaded.

“Now remember this,” Grigsby continued. “The teams had never played before and the Chiefs were three touchdown favorites with a flag flying upside down. That means, in international code, ‘distress.’”

The “distress” call went out early once again against the Eagles at Arrowhead on Friday night. This time in the first contest played at the Chiefs newly renovated home.

The Chiefs fumbled on the first play from scrimmage, giving Philadelphia the football on the Kansas City 22 yard line. When Eagles RB LeSean McCoy sprinted his way for an 18-yard touchdown just 50 seconds into the contest, things looked bad. When the Chiefs fumbled on their third play from scrimmage and punted on their fifth, things looked worse.

On the Chiefs next offensive series, QB <nobr>Matt Casselhttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr>’s pass hit off of TE <nobr>Tony Moeakihttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr>’s hands and landed in the arms of Eagles CB Trevard Lindley. That’s when it looked like the Eagles rout was on.

“I don’t know that it could start a lot worse than it did, both offensively and defensively,” head coach Todd Haley said after the game.

But in this instance, the rout wasn’t on.

The Chiefs defense came alive, forcing five consecutive punts after allowing an Eagles field goal near the end of the first quarter. Kansas City front-line players would notch their first turnover of the preseason, tally four sacks and exit midway through the third quarter holding a 14-10 lead; it was something that seemed improbable just a quarter and a half prior.

“They say in boxing that it’s not how hard you punch, it’s how you react after you’ve been punched,” Haley said. “We took a couple of pretty good body blows; they might have been a couple of head shots, hay-makers, whatever you want to say, but guys fought back and made plays.”

How many times have we seen the Chiefs start the game in a similar fashion over the past few seasons, only to get run out of the building?

Last year’s game against the Eagles immediately comes to mind, as does the game against the Giants and that 2008 drubbing in Carolina. There are other examples as well. Call it the “here we go again,” or “same old, same old” type of feeling, but things turned around differently at The New Arrowhead last night.

“I think it was just the ‘want to,’” LB <nobr>Demorrio Williamshttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr> said. “Early on we probably hung our heads down but I think the guys realized what type of team we have and guys came out and just fought to win the game. We are trying to win this year and trying to bring Arrowhead back.”

Whatever it was, it was something to build on.

While Williams and <nobr>Andy Studebakerhttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr> did their best to provide a spark with a pair of sacks, the Chiefs offense didn’t come alive until a bizarre penalty grounded the Eagles. Cassel connected on eight consecutive passes in a 16-play drive that was extended by the fourth-down delay of game penalty on Philadelphia’s punt return team. It was a play that finally kick-started the Chiefs offense.

The span of time between that penalty and when the Chiefs starters were removed from the game was the best that the Chiefs have looked as a team thus far in 2010. The team was physical on both sides of the football and made plays that amount to what it takes to win in the NFL.

The overall play before that penalty, and then after the removal of the starters, is what has to be nixed before the regular season begins.

Three to Like

QB Takedowns

Finally! The Chiefs recorded their first sack of the preseason, and they did it in pairs.

Demorrio Williams played like a maniac on Friday night, finishing with a pair of sacks, a diving pass breakup and five tackles. Andy Studebaker pitched in with two sacks of his own and DL <nobr>Dion Galeshttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr> added another quarterback takedown in the fourth quarter to give the Chiefs a quintet of sacks on the evening. It was the first time since September 23, 2007 (vs. Minnesota) that the Chiefs recorded five or more sacks in single game.

“That is really important,” Williams said of the Chiefs notching a handful of sacks. “Especially to put their offense in a second and long, third and long, things like that are huge. On third down we got some pressure on the quarterback and gave our other guys a chance to make plays.”

The numbers could have been even better, had the Chiefs finished off a few more chances at wrapping up Kevin Kolb, Mike Vick and Mike Kafka.

Gritty Defensive Effort

The defense as a whole turned in an extremely solid performance, especially in the second and third quarters.

They weathered an early storm from Philadelphia; a storm that was trying to turn ugly in a hurry. Physicality was at a pre-season high with big hits all over the field, including a wicked stick by <nobr>Derrick Johnsonhttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr>. The defense was blue collar, gritty, gutsy…whatever you want to call it…they played the game the way that it is meant to be played.

“Defensively we played together as a unit,” said S <nobr>Kendrick Lewishttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr>, who had an interception. “Everyone was on the same page and we blitzed them a little. Guys were getting free and making plays and applying pressure. On the back end we did our thing as far as coverage is concerned but as a unit, it all worked in our favor.”

In the end, holding Philadelphia to just 5-of-17 on third down made a big difference in the way the night went defensively.

Rushing Roles

The offense didn’t have its best day as a unit, but the Chiefs run game offers something to look forward to heading into the regular season.

Both of the Chiefs speedsters, <nobr>Dexter McClusterhttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr> and <nobr>Jamaal Charleshttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr>, averaged around six yards a carry and got loose in the open field. Situationally, the Chiefs bigger backs turned in some solid runs too. <nobr>Thomas Joneshttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr> was able to convert third-and-short situations, as was <nobr>Jackie Battlehttp://www.kcchiefs.com/assets/nflim...ticle-link.gif</nobr>, and Jones found the end zone on an 11-yard carry to get the Chiefs back on top in the third quarter.

It’s clear that the Chiefs are aiming to be a running football team.

Three for Improvement

Finding a Way to Win

How much better would Chiefs fans feel if Kansas City’s reserves could have just forced a three-and-out on Philadelphia’s final series? Or even a turnover on down in the Red Zone?

Instead of kneeling on a win, the Chiefs were dealt a loss in the game’s final minute.

For some, it doesn’t matter. The starters dug their way out of an early hole, took the lead and brought some swagger back to Arrowhead. For others, it doesn’t matter who was on the field; the Chiefs found a way to lose a tight game. Preseason or not, we’ve seen this outcome before and it’s not any fun.

Wherever you stand, there’s something to be said for the confidence that is built in successfully finishing off an opponent.

Turnovers Crush Chances

Before the Chiefs were on the board, they had already dug themselves into a two turnover hole. Kansas City’s turnover ratio is now at -7 (eight giveaways, one takeaway) this preseason. Dick Vermeil used to have some sort of turnover chart built with winning percentages based off of negative, positive and neutral finishes in the turnover department.

I don’t have that chart handy, but the Chiefs have lost the turnover battle in all three preseason games of 2010 and own a 0-3 record in those contests.

Philadelphia, by the way, scored their first 10 points on series’ that followed a Chiefs turnover.

Starting Fast

The Chiefs need to fix this broken record before the regular season gets under way.

no one in the media will discuss Cassel's performance...

he had a 64 QB rating for f sake and he barely gets a blurb

Jfc will everyone get over the ****ing Cassel obsession. He hasn't been good but he's way better than anything else we have so we are stuck whether you like it or not. Stop the gang piling, and beating a dead horse. Everyone can see that. You have any take that hasn't be mentioned like 48,000,000 times since this morning?

I wonder if Ol' Grigs really likes Zarda or not.

I wonder if Cassel's vagina is as rain-fresh as Taylor Swift's?

Ya know Cassel's been on the period, he got mad the other day & threw the ball fifty yards in practice.

Did he nail his favorite deep threat with it?


http://www.caufields.com/productimag...ages/50474.jpg

I am not going to accect a ****ing thing. Cassel sucks ass, and Pioli made a terrible error in judgement trading for him.

The only way we as fans should cut Cassel any slack is if he starts producing. If that happens, you will see a large amount of the pissing and moaning subside.

If we just accept what we have, the Chiefs will never win.

With the wind.

ROFL

Bring "it" in for a look?

It's sad.

Makes me think of Deberg and Green (career B/U players) with ****ing nostalgia...

might as well just let it go ... it's become as much about bugging other posters on CP as it is about Cassel.

look who's doing it, it amuses them to irritate people about pretty much anything. Not just Cassel.

my takes are all over the board, about both sides of the ball, with lots of specific compliments about players who played well...you're either too lazy to read the threads, or you read them and are just lying right now

i don't see jack shit from you discussing football, other then to whine about people who are actually discussing football

so I'll continue to post about whatever the **** i want..you can continue to not talk about football and cry about people who do

There were four passes from last night that getting an explanation from the team would help with:

The interception
The incompletion to Chambers
The sideline incompletion to Bowe
The incompletion to Jones

getting those cleared up would go a long way in helping to evaluate Cassel's performance last night.

The incompletion to Chambers was a well-thrown ball. He put it in a spot where it couldn't be intercepted. Chambers just didn't get there. Sorry...

Initial scouting reports show that It doesn't possess the mobility required to run crisp routes, but It's vertical is unmatched!

and the point about Cassel and the media is literal, and true

there is no detailed breakdown of his performance in the kc star...why?

why on earth wouldn't the newspaper talk about how our franchise QB performed?...he's the most important play on the team


but maybe they were going to write about him but didn't want to but up with all the crying chiefs fans who don't want it discussed

That was my take, too, but there were those who complained about Cassel's throw on the play.

and yet ...
<table class="data-table1" style="width: 747px; height: 137px;" id="result" cellpadding="0" cellspacing="0"><tbody><tr><th class="thd2">Rk</th> <th class="thd2 sortable"> Player</th> <th class="thd2 sortable"> Team</th> <th class="thd2 right sortable"> Comp</th> <th class="thd2 right sortable"> Att</th> <th class="thd2 right sortable"> Pct</th> <th class="thd2 right sortable"> Att/G</th> <th class="thd2 right sortable"> Yds</th> <th class="thd2 right sortable"> Avg</th> <th class="thd2 right sortable"> Yds/G</th> <th class="thd2 right sortable"> TD</th> <th class="thd2 right sortable"> Int</th> <th class="thd2 right sortable"> Lng</th> <th class="thd2 right sortable"> 20+</th> <th class="thd2 right sortable"> 40+</th> <th class="thd2 right sortable"> Sck</th> <th class="thd2 right sortable sorted order1"> Rate</th></tr> </tbody><tbody> <tr class="even"> <td>16</td> <td> Matt Cassel </td> <td> KC </td> <td class="right"> 34 </td> <td class="right"> 50 </td> <td class="right"> 68.0 </td> <td class="right"> 16.7 </td> <td class="right"> 235 </td> <td class="right"> 4.7 </td> <td class="right"> 78.3 </td> <td class="right"> 2 </td> <td class="right"> 1 </td> <td class="right"> 20 </td> <td class="right"> 1 </td> <td class="right"> 0 </td> <td class="right"> 4</td><td class="right">83.3 </td></tr> <tr class="odd"> <td>19</td> <td> Mark Sanchez </td> <td> NYJ </td> <td class="right"> 31 </td> <td class="right"> 48 </td> <td class="right"> 64.6 </td> <td class="right"> 16.0 </td> <td class="right"> 270 </td> <td class="right"> 5.6 </td> <td class="right"> 90.0 </td> <td class="right"> 2 </td> <td class="right"> 2 </td> <td class="right"> 23 </td> <td class="right"> 2 </td> <td class="right"> 0 </td> <td class="right"> 5</td><td class="right">75.9
</td></tr></tbody></table>

'Grigsby’s tale involved the Chiefs being three-touchdown favorites against Philly. The Eagles were woefully bad that year, 0-5 when they visited Arrowhead (they’d finish 2-11). Unfortunately, for the Chiefs, there was a pre-game alarm as to what was about to come.'

I remember lessoning to the pre-game show of that game back in 72 :skip: and Grisby was going on and on about how much 'more experience' the Chiefs players had compared to the Eagles. The Chiefs had always had a good team but during that game the Super Bowl Champion Chief players hit the old age wall. After that it was 14 years of sucky Chief teams.

Colb had a 39 rating. We win.

We can't get off of how much Cassel sucks because you can't ****ing win in the NFL with a QB that sucks.

This is a QB driven league, and we have a useless ****ing dumbass that rides in the back of the short bus.

No Steve Fuller?

If they start hammering Cassel, the media will lose what little access they get now. Pioli knows how to use the carrot-and-stick with the KC media.

Well Cassel is what we got so I think its just best to just try to accept him and hope for the best. What else can you do if you really think about it? At least thats my attitude to this point.

But hey if people want to vent. Just vent. Its all good. Let it out. Who is one to tell you how you should post? That is no offense to you Dave Lane.

But yeah as of now I see plenty of reason to complain about him. He's been a disappointment thus far but there is room for improvement. Lets see how he does over the course of a season. Sometimes it takes time to judge a player, and its easy to jump the gun early and give up on guys. I've been guilty of that in the past. Im not defending him, but lets just see if he can get better with a better cast of players and coaches around him.

Lets see if he can understand and adapt to the playbook well. Lets see how he works under the tutorledge of a good offensive coach. Remember he didn't have Weis last year was forced to kinda learn things on his own. And there were a lot of changes last year in our offensive personnel throughout the course of the season. It's hard to adjust and adapt to a new environment where there is constant change and where you are practically learning on your own. Im not trying to make excuses for the guy, but I think its important to remember these little factors and not disclude them. They could affect the progression of a players development.

This would be a great post if you would compare them 5 years from now. I bet one is out of the league and the other one is playing ball for respective team.

You are correct. Sanchez will leave the NFL for the movies and star in Baywatch 2015.

Nothing about the checkdown, knocked down, drifting back INTO the pocket ****ING flea flicker?

That play transcended Benny Hill to an impromptu Fellini film.

If Just Fisting Myself actually cared to read or watch the game, he'd realize that you really don't need a coach speak explanation for the pick. Cassel made a bad read and threw a bad pass. It was way behind the receiver. However, it also didn't help that Brokaki floated into Chambers' area, and thus brought two other defenders into the play.

just manage the game! and he always has to take that extra step before he throws the ball?

Bob Dole cares even less about the loss, since the clock should have run out roughly 40 seconds before it did... (See the 4:22 mark mystery clock stoppage.)

And the flag thrown that stopped the clock right before Philly scored. Of course the flag was picked up but the Eagles were already lined up and ready to run the next play. That saved them about 12 seconds and allowed them to have a play called so thery didn't have to run a spike play. Total BS.


PhilFree:arrow:

That's true, Mr. Just Passin' By. I'd consider those breakdowns helpful, as well.

However, I would also like an explanation for the enormous and growing damp spot that appeared in Cassel's crotch during the first series.

FAX

The lineman failed to engage the opposing lineman, thus allowing the defender to get his hands in the air. No further explanation is needed.

Cassel is a below average quarterback. No further explanation needed.

The QB always gets far more blame than he should when a team is losing. Watching this board lose its collective mind has served to demonstrate that once again.

Losing's got nothing to do with it. If the team were winning, I'd still be shaking my head at the way Cassel looks like he doesn't know what to do on any given play.

Cassel hasn't been anywhere near as bad as he's been portrayed on this board.

Yeah, sure, dumbass.

If we are talking about the collective portrayal, he's been worse.

Cassel AND Sanchez suck.

He's been barely adequate at times. Most of the time not, though.

he was scared that charles was gonna keep fumbling the ball?

that was the only play of the series
Posted via Mobile Device

Yes, absolutely no need to explain why a QB who throws nowhere but the flat with any accuracy turned a ****ING flea flicker into a checkdown pass after wandering back up into the pocket, for no more reason than it seemed the easiest place to which to mosey.

Why don't we go full reerun and have those RB receiving passes in the flat run right back to the middle of the field to be tackled by a DLman?

That's a rich explanation right there, Mrs. Cassel.

maybe some here should watch the replay, the long reciever was COVERED from what i saw on the flea flicker.
Posted via Mobile Device

Doesn't matter. The deep receivers could all have dropped dead of heart attacks and people here would still be complaining about Cassel. It's not about figuring out what happened. It's about bitching about Cassel.

yep just watched it again.

chambers was covered even trent said so.

cassel didnt wander anywhere. he stepped into the throw to chambers and didnt throw it. then he stutter stepped and threw it to bowe on a crossing route. the line let the defender knock it down.

but the long ball (chambers) had two defenders in the area.
Posted via Mobile Device

This. Plus the Chiefs do not have a legit starting QB on the roster. They need to fix that.

I touched the issue on this thread.

http://www.chiefsplanet.com/BB/showt...232598&page=19

But will copy and paste it on here, just to save everybody the trouble.

bowe was the right read there, he had a lb iirc running with his back to the qb and had a step on the defender covering him. he was open when the ball left matts hand.
Posted via Mobile Device

Oh, I wasn't questioning your analysis. I was just noting that it doesn't matter to a large group of posters on this board.

our 63 million dollar franchise QB, who by consensus is surrounded by new 'playmakers' in DMC and Brokaki, earns a 64 QB rating in his longest outing of the preseason in which he throws for 85 yards (including a gift int on the goal line that a ham handed LB dropped)...

and he's being praised, and simultaneously absolved of all responsibility, by his fart sniffing pats fan stalker...


can someone explain how a QB puts up such shit numbers and is then praised for playing well?

Cassel developed some bad habits over the course of last season, because he spent the first half of the year running for his life and having to throw the ball to people who usually weren't open, and who often couldn't catch the ball even when they were. His play still shows the effects of that, because it's obvious that he has absolutely no confidence in that line. It's the sort of thing happens with most quarterbacks during games when the team is getting overwhelmed. It happened enough to Cassel last year that he's expecting it every game now, and the important thing moving forward is what he does about it, because he definitely let it get to him over the course of last season. His attitude on the field is also something I'd be worried about if I were the coaching staff, because he's at the point where he's letting every failed play get to him in a way you can see on the field, and his teammates are certainly going to notice that.

But noting those issues, and bitching about everything the man does, are two different things. He made some very nice throws against Philadelphia, and he had the team in the game when he left the field, yet some of the posters here are acting as if he went 0-for-60 and knifed six little old ladies during the timeouts.

Well, Can:

If the incomplete to Chambers is on Chambers, that would have had an impact on Cassel's numbers despite his making a good throw.

If the incomplete to Jones was because Jones got caught up, or because of a read difference due to his inexperience in the system, that would have a negative impact on Cassel's numbers despite his making the right throw.

If either Moeaki or the wide receiver was in the wrong spot, that's not on Cassel, because 2 receivers had run routes into the same 5 yard area. Even if he wasn't in the wrong spot and the throw was a bit off, moeaki should have caught the damned ball, which would have removed the INT from Cassel's sheet and would have added yards.

If the incomplete to Bowe was because Bowe was too slow in adjusting to coverage, or because he didn't come back properly, that would impact Cassel's numbers despite it being the right throw.

I also didn't absolve Cassel of responsibility. I posted: "getting those cleared up would go a long way in helping to evaluate Cassel's performance last night". That's different than the take you had in the game thread, for example, where you decided to bitch at Cassel over the incompletion to Chambers.

LMAO Quality work, Sir.


Would anyone else really like to pistol-whip JPB at this point?

I mean; ****...:shake:

Expecting Brokaki to catch that ball is laughable. A better approach would be not to expect your "franchise" QB to complicate a horrible decision by throwing a horrible ball.

And if Cassel is still "suffering" from poor line play at the beginning of last year, he's a bigger waste than I assumed.

That ball shouldn't have been thrown in there in the first place. It was well defended by the Eagles.

watch is again and look for Bowe being open on the crossing pattern over the middle.

single coverage
cornerback was 2/3 yrds behind him on his hip
no linebackers between cassel and bowe(that i could see)

easy completion and maybe a touchdown if Bowe turns it upfield quickly

Who the **** would be playing qb for us right now then? Brodie? With this o line?

Bull ****ing shit, the entire purpose of the flea flicker is to; 1) give the QB some room to launch on a variation on a 7 step drop, and 2) launch downfield to WRs on burners, on the hope that either the WRs superior speed or a hitch from the DB reading run creates separation.


List for me the number of times in the HISTORY of the NFL where a flea flicker EVER resulted in the QB back up in the pocket, finding the checkdown and throwing into the line. Feel free to go back as far as you want.

I've been watching for 20 years, and seen my share of NFL Films, and had never seen it before Cassel.

Of course 30 yard hail Mary's to the less than inviting arms of the uprights had been a scarce tactic until recent, too.

If the CB doesn't bite on the fake, you don't throw the deep ball. That's smart on the part of the QB, and it happens. Brady's been in that situation numerous times in recent years. Your "throwing into the line" argument is the fault of the offensive lineman, who left the D-lineman disengaged.

dont need to watch it again. i already said bowe was open and that was where cassel was going with the ball. read all my posts.

and there was a lb who was running to bowe, but his back was to cassel and bowe beat him too. cassel threw the ball to bowe it just got knocked down.
Posted via Mobile Device

If it's single coverage, he damn well better throw the ball. Let the WR try to make a play...maybe get PI called...at the very least show the threat of the deep ball and stretch the field.

****, the last option can be just as beneficial as a completion, especially as the game progresses.

So I understand your assertion as clearly as possible, you are saying that Brady has not only run numerous flea flickers in recent years, but checked down on numerous flea flickers in recent years.

Since my best guess estimate is that teams average 1-2 flea flicker attempts a year, is it your position that NE runs an inordinate number of them in 'recent years' or that the general sense of 'numerous' and 'recent' are liberalized for the purposes of this discussion.

wow. no seperation from db to wr should mean no throw. he stepped into a throw to chambers and seeing him covered he held the ball then stutter stepped into a throw to the open bowe who was running a crossing route. the d line knocked the ball down.

is that a fair assessment? opinions?
Posted via Mobile Device

Wasnt one of Pioli's explinations for taking a safety at 5 and a nickle in the 2nd, that the league was turning into more of a spread/pass happy league? yet we're reverting back to a running club.

chambers had a defender contacting him and another about 3-4 yards ( in my estimation ) to the plays left. also on about the same yardline. so he was basically double covered especially by the time a pass would get there.
Posted via Mobile Device

you know what who gives a ****? the wr was covered, which if you would have watched the chiefs replay you would know. probably wouldnt make a difference though.

you are wrong. cassel made some bad plays but that wasnt one of them unless you blame him for getting the ball batted down. He made the right read.
Posted via Mobile Device

Give it up, Sauto; the man ain't The Man.:p

The central concern is this starting to look like, even if Weiss forced the issue and sent every single eligible receiver on a go route, Cassel would try to check down to to an O-lineman.

well if they were all double covered what would be the right play? (and i know its not possible but we arent really being realistic in this scenario)
Posted via Mobile Device

much has been said fairly and i havent said shit. but when its not fair or just totally off base ( such as here) ill say something.

cassel gets bashed for everything im surprised that he hasnt been blamed for page not showing up
Posted via Mobile Device

Serious question Jason... Do you really like what you see in Cassel?

not all the time. i see some things he does right. i see some he does wrong.

im not naive enough to blame it all on him. in this case chambers was covered. he made the right read, nothing to complain about unless you blame him for the dlineman that albert was blocking knocking it down.

helll i said the other day that he needs to shit or go. not play good enough to save his job.

step up when the bullets fly or die and be gone after this season.
Posted via Mobile Device

Fair enough. I have not had time to read everything... everyweek. There seems to be a small faction of the Planet that seems to be defending Cassel at every turn. Didn't know if you were one of those or not, but I have seen you defend him quite a bit.

I just see a lot more to not like that to like. Wished it wasn't that way, but the guy just does not make me feel good about our offense.

i do end up defending him quite a bit.

if i agree about a bad play he had i usually just dont chime in. what would be the point? 100 posts say the same thing.

if people are bitching and totally off base i put my opinion out there.

i also say something when every thread turns into a cassel bashing. even unrealated threads. THAT takes away from the planet IMO.
Posted via Mobile Device

A flea flicker takes a long time in to develop, relative to most plays in the NFL, and that play, because Chambers didn't get open and Matt Cassel drifted toward the LOS to checkdown even took longer, and we are expected to blame an O-Lineman for not sustaining his block for that amount of time?

Thank you and I agree. Seriously he hasn't been good but good god people try to act like like a frikking adult not a 2 year old. We are stuck there is nothing better out there we can get. He's so far been below average and has acted scared. I say good if that's the way he ends the season we will part ways with him and get a new possible QBOTF in here and hopefully we will finally hit on one.

Myself I'm still hoping that he improves and proves all of us wrong. I refuse to get my dander up over it till there is a better option. If we get somebody better then I'll get upset if he's still playing, till then psssfft...