- Thread starter
- #1
Caliskinsfan
Burgundy & Gold Forevah
- 43,311
- 9,030
- 533
- Joined
- Aug 15, 2013
- Hoopla Cash
- $ 4,569.00
- Fav. Team #1
- Fav. Team #2
- Fav. Team #3
It’s only Week 3 of the preseason and the rumor mill is on fire already. Is there any truth to the latest, that Jay Gruden left RGIII in the game intentionally and that it is personal between the two of them?
– Tammi Armstrong
It’s never too early for the circus to roll into town, is it? Yes, the rumor mill has already cranked up. But you’ve got to take a lot – especially from some outlets – with a grain of salt. That was a really silly report that came out, that Gruden left Griffin in the game because it was personal. Anyone who thinks that was the case is someone who isn’t plugged in on what’s going on behind the scenes at Redskins Park. Yes, it was surprising to see Gruden trot his starting quarterback back out there for a fourth series, when the first three possessions were nothing short of a debacle. But it wasn’t personal, it was mandated. Jay Gruden has received clear instructions that Griffin is his quarterback, and that all Griffin needs is more work and time to become comfortable in the system.
Remember, Gruden wanted to stage an open competition for the job. But between the time of his final press conference of 2014, in December, and his first of 2015, in February, the tune had changed. Daniel Snyder and Bruce Allen aren’t ready to give up on Griffin, multiple people within the organization insist. Scot McCloughan believes that more than the quarterback situation needs fixing, so he’s going about fortifying the rest of the roster while evaluating Griffin. Allen is on record saying Griffin is a young quarterback that just needs time. Time is what Griffin is getting – even if that means going back into a game where he’s getting thrown around like a rag doll. Gruden did subject Griffin to risk of injury, but Griffin didn’t do much of anything to protect himself, either. Gruden felt like his quarterback badly needed something positive to build on, both for his confidence and for the confidence of the other offensive starters. That’s why he continued to play Griffin. Even people within the organization, who aren’t sold on Snyder and Allen’s assessments, agreed that Griffin needed work.
So, no. Beyond silly to think that Gruden wanted to send Griffin out there to get him hurt so he could go with Colt McCoy or Kirk Cousins. Gruden is a former quarterback, who has dealt with serious injury. He wouldn’t wish that on anyone. And he didn’t send him back out there to cause the quarterback more embarrassment. Gruden doesn’t have a problem with Griffin personally, even despite No. 10’s quirks. He just wants him to execute and win games. Does the coach wish he could move on and start a different quarterback? Yes. But he’s doing what he’s told, and trying to do everything possible to prop Griffin up. Would he be happy to see Griffin have an awakening and start lighting it up again? You bet. Would he be relieved if he could call the shots at quarterback and give his team the best chance to win? Yes, again. But he isn’t trying to solve the Griffin dilemma in a conniving way.
The Redskins exercised the option on Robert Griffin’s contract, which, if Griffin gets hurt, means the Redskins would be on the hook for $16 million. If that happens, how much of the $16 million would count against next year’s salary cap? If the full $16 million would count against next year’s salary cap, which would be a heavy hit against the salary cap, can the Redskins bench Griffin, who has performed poorly in preseason and has shown he is injury prone, so that the $16 million would not count against next year’s salary cap?
– Al Ezrin, Murrells Inlet, S.C.
Yes, all $16 million would count against the cap if Griffin suffered a serious injury and wasn’t able to pass a physical at the start of the 2016 league year because he was still rehabbing. Because of that, multiple people close to the franchise believe that Griffin will be on a short leash this season. If he’s performing poorly, taking unnecessary sacks, putting himself at risk of injury and losing games, then he’ll get the hook, they believe. A cap hit of $16 million for a guy who’s not the answer at quarterback – and if seriously injured, may never play again – is too hefty to absorb. The question is how long will Griffin have to exhibit that type of poor play before he gets the hook? It’s hard to say. Some of those same people with ties to the team believe the quarterback will get four games. It’s really a question of how much Snyder and Allen need to see before coming around to everyone else’s point of view. Could be longer.
Why is everyone in such a panic about the first string offense? It’s only been two pre-season games, DeSean Jackson has been out, Trent Williams missed the Detroit game, they’ve had injuries at the tight end position. And on top of everything the first game against Cleveland they moved the ball extremely well. Let’s also not forget the Lions boast a possible top-five defense even without Suh. In your opinion, is it really time to start panicking and talking about quarterback controversies?
– Rob Fox
I think the reaction is a culmination of everything we’ve all seen in 2013, 2014 and now this preseason. Griffin hasn’t played effectively since his rookie season. He’s gotten benched for non-injury reasons twice. He hasn’t led the starting offense to a touchdown in the preseason since his rookie year. Even without Jackson, this unit should be moving the ball and picking up first downs here and there and scoring a couple touchdowns. They never crossed midfield against Detroit. That defensive front is good, but not that good. The final series came against the second-string defensive line. Colt McCoy then came in and started moving the ball against that same front.
So that’s why there’s concern about quarterback and the first-team offense. Yes, Williams was injured, and that makes a big difference, but things shouldn’t have gone as poorly as they did. Let’s see if they can bounce back and finally put something together against Baltimore.
The Pierre Garcon should’ve-been-touchdown against Cleveland would have changed the narrative, to a degree. But I have a suspicion that what we saw against Detroit is closer to reality. Again, let’s see how this third preseason game goes. Even after that, I wouldn’t recommend panicking. But, you might want to get a backup hobby plan for your Sunday afternoons, just in case more carnage ensues and drives you away from your TV set.
– Tammi Armstrong
It’s never too early for the circus to roll into town, is it? Yes, the rumor mill has already cranked up. But you’ve got to take a lot – especially from some outlets – with a grain of salt. That was a really silly report that came out, that Gruden left Griffin in the game because it was personal. Anyone who thinks that was the case is someone who isn’t plugged in on what’s going on behind the scenes at Redskins Park. Yes, it was surprising to see Gruden trot his starting quarterback back out there for a fourth series, when the first three possessions were nothing short of a debacle. But it wasn’t personal, it was mandated. Jay Gruden has received clear instructions that Griffin is his quarterback, and that all Griffin needs is more work and time to become comfortable in the system.
Remember, Gruden wanted to stage an open competition for the job. But between the time of his final press conference of 2014, in December, and his first of 2015, in February, the tune had changed. Daniel Snyder and Bruce Allen aren’t ready to give up on Griffin, multiple people within the organization insist. Scot McCloughan believes that more than the quarterback situation needs fixing, so he’s going about fortifying the rest of the roster while evaluating Griffin. Allen is on record saying Griffin is a young quarterback that just needs time. Time is what Griffin is getting – even if that means going back into a game where he’s getting thrown around like a rag doll. Gruden did subject Griffin to risk of injury, but Griffin didn’t do much of anything to protect himself, either. Gruden felt like his quarterback badly needed something positive to build on, both for his confidence and for the confidence of the other offensive starters. That’s why he continued to play Griffin. Even people within the organization, who aren’t sold on Snyder and Allen’s assessments, agreed that Griffin needed work.
So, no. Beyond silly to think that Gruden wanted to send Griffin out there to get him hurt so he could go with Colt McCoy or Kirk Cousins. Gruden is a former quarterback, who has dealt with serious injury. He wouldn’t wish that on anyone. And he didn’t send him back out there to cause the quarterback more embarrassment. Gruden doesn’t have a problem with Griffin personally, even despite No. 10’s quirks. He just wants him to execute and win games. Does the coach wish he could move on and start a different quarterback? Yes. But he’s doing what he’s told, and trying to do everything possible to prop Griffin up. Would he be happy to see Griffin have an awakening and start lighting it up again? You bet. Would he be relieved if he could call the shots at quarterback and give his team the best chance to win? Yes, again. But he isn’t trying to solve the Griffin dilemma in a conniving way.
The Redskins exercised the option on Robert Griffin’s contract, which, if Griffin gets hurt, means the Redskins would be on the hook for $16 million. If that happens, how much of the $16 million would count against next year’s salary cap? If the full $16 million would count against next year’s salary cap, which would be a heavy hit against the salary cap, can the Redskins bench Griffin, who has performed poorly in preseason and has shown he is injury prone, so that the $16 million would not count against next year’s salary cap?
– Al Ezrin, Murrells Inlet, S.C.
Yes, all $16 million would count against the cap if Griffin suffered a serious injury and wasn’t able to pass a physical at the start of the 2016 league year because he was still rehabbing. Because of that, multiple people close to the franchise believe that Griffin will be on a short leash this season. If he’s performing poorly, taking unnecessary sacks, putting himself at risk of injury and losing games, then he’ll get the hook, they believe. A cap hit of $16 million for a guy who’s not the answer at quarterback – and if seriously injured, may never play again – is too hefty to absorb. The question is how long will Griffin have to exhibit that type of poor play before he gets the hook? It’s hard to say. Some of those same people with ties to the team believe the quarterback will get four games. It’s really a question of how much Snyder and Allen need to see before coming around to everyone else’s point of view. Could be longer.
Why is everyone in such a panic about the first string offense? It’s only been two pre-season games, DeSean Jackson has been out, Trent Williams missed the Detroit game, they’ve had injuries at the tight end position. And on top of everything the first game against Cleveland they moved the ball extremely well. Let’s also not forget the Lions boast a possible top-five defense even without Suh. In your opinion, is it really time to start panicking and talking about quarterback controversies?
– Rob Fox
I think the reaction is a culmination of everything we’ve all seen in 2013, 2014 and now this preseason. Griffin hasn’t played effectively since his rookie season. He’s gotten benched for non-injury reasons twice. He hasn’t led the starting offense to a touchdown in the preseason since his rookie year. Even without Jackson, this unit should be moving the ball and picking up first downs here and there and scoring a couple touchdowns. They never crossed midfield against Detroit. That defensive front is good, but not that good. The final series came against the second-string defensive line. Colt McCoy then came in and started moving the ball against that same front.
So that’s why there’s concern about quarterback and the first-team offense. Yes, Williams was injured, and that makes a big difference, but things shouldn’t have gone as poorly as they did. Let’s see if they can bounce back and finally put something together against Baltimore.
The Pierre Garcon should’ve-been-touchdown against Cleveland would have changed the narrative, to a degree. But I have a suspicion that what we saw against Detroit is closer to reality. Again, let’s see how this third preseason game goes. Even after that, I wouldn’t recommend panicking. But, you might want to get a backup hobby plan for your Sunday afternoons, just in case more carnage ensues and drives you away from your TV set.
