Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Great game indeed.
No it wasn't.
Sean Payton cost us that game. It was easily the worst playcalling game he's had since 2008. I love the guy and always will, but this one is 90% on his shoulders (other 10% being on the refs).
That said, it's just one game and I more than expect this team to bounce back. We'll be 9-1 by the time we face San Francisco.
And what percentage of the blame falls on the shoulders of Rob Ryan? Because the Saints defensive coverage in the last few minutes of that game was abysmal.
The Patriots, trailing by one, turned over the ball on downs with 2:46 left in the game. Brady, trailing by four, then threw an interception with 2:24 left. And yet the Patriots somehow beat the New Orleans Saints 30-27 anyhow.
And what percentage of the blame falls on the shoulders of Rob Ryan? Because the Saints defensive coverage in the last few minutes of that game was abysmal.
There's virtually zero ticky-tackness on that call. The rulebook clearly states you can't ever do that, and it was blatantly done (the offending player has admitted he screwed up and broke the rules). How is that ticky tack? The only reason we haven't seen it called yet is because it's a new rule this season (one that was pushed for by the players no less) and this is the first time it was done.Despite me bitching about the refs last week, I don't agree with the call in the Patriots/Jets game. It might have been the "correct" call by the rule book, but like in basketball when it comes to ticky-tacky fouls when the game is on the line, you have to let that one go.
I hope we find a new quarterback soon. Alex Smith is the only reason the Chiefs aren't blowing these teams out. That D is special, they deserve a better offense.
The rules do not change at the end of the game. If it's a foul midway through the first quarter, it's a foul in overtime.
Also, I love Steve Smith.
Rules are rules. The guy blatantly broke the rules and admitted it after the fact. I don't get how you can say "ok whatever, you broke the rules right in front of the ref on the biggest play of the game, lets not call the flag." If that's the case then the 9 guys on the line for Field Goal tries should just tackle the guys trying to block the kick, since that's legal in your mind.I understand your point of view, but if it were the other way around I think you'd have some trouble feeling the same way.
Or it hasn't happened because the new rule was well known by the players since they were specifically told of the new rules during training camp.I just thought it was weird that was the first time that foul was called throughout 6 weeks of NFL play. It had to have happened before, yet that's the one time a referee sees it? Just strange and I still don't agree with making the call in that situation and deciding the game on something so trivial.
I can't vouch for that since I didn't see the game last week, but all I know is they had called the game relatively tight all game. Calls that were borderline were getting called for most of the game (including an OPI on Stephen Hill on a touchdown catch that was a flop).And for the record, I do acknowledge the karma. All the awful calls against the Saints last week, and then the CLEAR holding call that wasn't made on Brady's game winning TD pass...
But it did affect the kick. It created an artificial, illegal pressure. Sure they didn't block it, but they got closer to the ball then they should have.So it's not like I have a biased point of view here. I just don't agree on deciding a game on a call that didn't affect the play one bit. Now if that dude blocked or disrupted the kick in anyway, then fine... fair call, but that didn't even come close to happening and I just personally feel you let the players decide the outcome, not the refs.
So in your mind do you not call a foul on a basketball defender if the player makes the shot?