Who ya going to blame when a DEFENSE can NOT hold an OFFENSE to under 30 points?
How many points did the Eagle offense score? I think it was 20 so you're happy ,right?
Who ya going to blame when a DEFENSE can NOT hold an OFFENSE to under 30 points?
if I remember correctly philly the week before was shut out on of all their scores came on st and df so i'm not sure holding them to 20 is so good.
And giving the Eagles the ball on the 24 was a guaranteed 3 points, D gave up the rest. Basically the D gave up 17How many points did the Eagle offense score? I think it was 20 so you're happy ,right?
I think it is bogus when the QB throws a ball up for grabs and the receiver initiates contact either trying to get back to the ball or heading straight at the DB. If the DB is maintaining position it should be on the receiver - especially when the QB is simply getting rid of the ball to avoid a sack. Those balls were nowhere near the receiver that got the call.Foles got lucky on several throws for sure. That is garbage QB play in my opinion. I didnt see any PI that were bad calls really, just lucky nonsense QB play. The D did play well enough to win for sure. Bodes well for the rest of the season if the D can get on the same page.
If the Whiners dumb OC ever realizes his team needs to run the ball 40 times a game they will be very tough. The longer they try to make themselves a pass first team they will struggle. Still, in the trenches, this will be a real test for the Rams.
I don't disagree with you, but, it's how the rule is written.I think it is bogus when the QB throws a ball up for grabs and the receiver initiates contact either trying to get back to the ball or heading straight at the DB. If the DB is maintaining position it should be on the receiver - especially when the QB is simply getting rid of the ball to avoid a sack. Those balls were nowhere near the receiver that got the call.
Well it was a home game for them and they had a week to fix some of the things that went wrong at SF ... and one of their offensive scores was a short field due to Stacy's fumble. Not saying it was a great defensive performance, but it wasn't horrible and it wasn't as bad as the score made it look, considering they had 14 points of D/ST.
I don't disagree with you, but, it's how the rule is written.
should have been an interception, Foles was out of this world lucky..There was one play where Foles threw up a duck whilst Quinn was hanging off his leg. How is that not classed as a hit?
Well, the defender is allowed his position, but, also cannot impede a receivers progress....so the rule contradicts itself. If the WR stops running or reverses into the DB there really should not be a foul but it probably get called....especially now.But I actually don't think it is. I haven't read it in years but I think there is wording about initiating contact and allowing the defender to hold his established path or position. Of course with the NFL wanting more scoring, there could be either some interpretation or wording changes. I don't know. But we all know refs are allowed to interpret. Those plays IMO were obvious that the QB was simply avoiding a sack and you just CAN'T bail him out with those calls.