Dude was a terrible coach. They underperformed every year with him there.
Sure, but aren't the Bills historically famous for under performing?Dude was a terrible coach. They underperformed every year with him there.
Yes, they are the mstateglfr of the NFL, but that doesn't mean we shouldn't all expect better.Sure, but aren't the Bills historically famous for under performing?
They had no WRsIt was time. I think he’s an ok head coach, but they underperformed this year given how manageable their schedule was and how open the AFC field was.
They can hope for better, but their expectation should be annual heartbreak.Yes, they are the mstateglfr of the NFL, but that doesn't mean we shouldn't all expect better.
The have MSU legend and Mike Leach disciple Tyrell ShaversThey had no WRs
They were pretty decimated with injuries. At this point who’s better?It was time. I think he’s an ok head coach, but they underperformed this year given how manageable their schedule was and how open the AFC field was.
Maybe not choke their way to a six seed where they had to go on the road in the playoffs?Josh Allens' banner day....what could he do about that?
They also were completely hosed by historically bad officiating which cost them a bid to the AFC Title game. Were they going to fire him next week too if he didn’t beat NE?They were pretty decimated with injuries. At this point who’s better?
They had no WRs
The don’t care, they just make movesIsn't the NFL sort of like college football this year, it's a terrible time to have to be looking for a new head coach?
Shocking with the appeal of the Buffalo media market, weather, and New York taxes that he couldn't do better there...Dude was a terrible coach. They underperformed every year with him there.
Those were the right calls.They also were completely hosed by historically bad officiating which cost them a bid to the AFC Title game. Were they going to fire him next week too if he didn’t beat NE?
Which ones?Those were the right calls.
The Cooks call was right too. You have to survive through the ground on a catch. He didn't. It never touched the ground and ended up in McMillan's possession.Which ones?
I’m not talking about the PI’s. Those were correct but should not have even come onto play.
The Cooks-McMillan call was the joke of the century.
It's completely bizarre. The NBA also has a history of recycling coaches, but it's nowhere near the level of the NFL where a head coach gets fired one day only for the league to treat it like the ten million dollar sweepstakes 24 hrs later as they're trying to figure out where he'll landThe NFL is a weird beast, but on the surface this appears to be unfathomably stupid.
The Cooks call was right too. You have to survive through the ground on a catch. He didn't. It never touched the ground and ended up in McMillan's possession.
Only the wooliest of Bills fans would disagree with this. Probably the easiest call of the day.
ETA:
At the 23 second mark you can see the ball coming loose before Cooks hit the ground anyway.
You forgot the *******The have MSU legend and Mike Leach disciple Tyrell Shavers
He consistently makes questionable decisions. Just in the past two weeks he’s made big mistakes.They were pretty decimated with injuries. At this point who’s better?
The Cooks call was right too. You have to survive through the ground on a catch. He didn't. It never touched the ground and ended up in McMillan's possession.
Only the wooliest of Bills fans would disagree with this. Probably the easiest call of the day.
ETA:
At the 23 second mark you can see the ball coming loose before Cooks hit the ground anyway.
The ground doesn't have to cause the ball to come out. If you jump up, catch a ball, land on your backside, and the ball comes out, it's an incomplete pass, whether a defender is near you or not. You have to survive contact with full possession through the end of the movement for it to be catch.The ground is not what caused the ball to come out, therefore the “surviving the ground” argument holds no water.
There is clear and indisputable evidence that Cooks was down with possession. Knee on the ground, ball tucked, defender was touching Cooks but not even touching the ball at that moment in time. Defender reached in and snatched the ball after he was down with possession.
The notion that if you as an offensive player can have a knee on the ground with possession of the ball, therefore cannot advance the ball any further…..yet somehow a defender can just rip the ball away and run it back the other way for a TD is absolutely preposterous.
I think this play is a case of the original call stands either way. I don’t see evidence to overturn either a catch or an interception.The ground doesn't have to cause the ball to come out. If you jump up, catch a ball, land on your backside, and the ball comes out, it's an incomplete pass, whether a defender is near you or not. You have to survive contact with full possession through the end of the movement for it to be catch.
There is no 'clear and indisputable evidence that Cooks was down with possession.' In fact, there's no evidence of this at all, because he wasn't. This was called that way on the field and upheld with video review. You're seeing what you want to see, and not what happened.
The defender didn't snatch the ball from Cooks...they didn't exchange possession like a handoff. He pried it loose and then gained possession of the loose ball before it ever hit the ground. I literally provided you the video with multiple angles of this and you are still arguing against it. Again, seeing what you want to see.
But that’s not what happened. There’s no evidence at all that the ball was moving or that Cooks didn’t have possession before the defender intervened. Simply put, Cooks wasn’t even given the opportunity to “survive the ground” because egregious contact was made by the defender to wrestle the ball away before he even fully hit the ground.The ground doesn't have to cause the ball to come out. If you jump up, catch a ball, land on your backside, and the ball comes out, it's an incomplete pass, whether a defender is near you or not. You have to survive contact with full possession through the end of the movement for it to be catch.
There is a clear still frame, which I know you have seen, that shows Cooks with his knee on the ground, McMillan touching him, and the ball tucked after he caught it. He’s got a knee on the ground, he’s holding the ball, he’a touched by the defender. He’s 17ing down. If he’s NOT down, then by definition, if McMillan hadn’t pulled the ball away, he could have in theory just gotten up and continued running for a TD.There is no 'clear and indisputable evidence that Cooks was down with possession.' In fact, there's no evidence of this at all, because he wasn't.
I’m not a Broncos or Bills fan. There’s no preference to me what I see. I’m seeing what happened. As for the “review”, they didn’t even stop play and go under the hood to see the slow motion. It was a farce. It was a bang-bang play that was called wrong on the field, and the whole crew had to scramble quickly for a bogus justification to prevent a total mutiny from happening on the home field of the AFC #1 seed. Because it absolutely was going to guarantee a Bills victory if it was overturned and ruled a catch.This was called that way on the field and upheld with video review. You're seeing what you want to see, and not what happened.
The defender didn't snatch the ball from Cooks...they didn't exchange possession like a handoff. He pried it loose and then gained possession of the loose ball before it ever hit the ground.
I literally provided you the video with multiple angles of this and you are still arguing against it. Again, seeing what you want to see.
We’ll never know, because they didn’t stop play long enough to dive into the multiple camera angles and slow motion replays. League wanted to quickly just rubber stamp it and move on, because they knew the shítshow that would ensue if they didn’t.I think this play is a case of the original call stands either way. I don’t see evidence to overturn either a catch or an interception.
Thank goodness for that. We were spared 10 minutes of endless slow and stop motion replays and speculation from the announcers and the "rules expert" before a decision was finally announced that would be at least as controversial as it is without the review.We’ll never know, because they didn’t stop play long enough to dive into the multiple camera angles and slow motion replays. League wanted to quickly just rubber stamp it and move on, because they knew the shítshow that would ensue if they didn’t.
The 23 second mark in the video above proves you wrong and renders every other letter you typed in that wall of text irrelevant. You're wrong. Throwing walls of text at the problem isn't going to make it better.But that’s not what happened. There’s no evidence at all that the ball was moving or that Cooks didn’t have possession before the defender intervened. Simply put, Cooks wasn’t even given the opportunity to “survive the ground” because egregious contact was made by the defender to wrestle the ball away before he even fully hit the ground.