Demi wrote:
No, it's not ok to pay either of them that much. But you said if it was an issue you'd be on board, it's an issue. We're cutting players because of how much they're making and our salary cap status.
We didn't have to cut either player. There's a difference between asking them to take a pay cut to make their salary commensurate with their value/ability and "having to cut them" to pay their salary.
Demi wrote:
You don't ask him to take a pay cut before cutting him if it isn't a cap issue. So he's ok to be on the roster and starting at a lower salary but the same other issues? We had to be under the cap by Thursday of that week, and suddenly it comes up. There were other issues, but if he had agreed to take a pay cut, he was still on the roster. Despite being 400 lbs and a bad practice away from a heart attack. And then left tackled a super bowl team.
Yes you do. Again, it is the value of the player that determines what he is paid. Just because a player is not worth what you originally offered for him, doesn't mean that he has NO value. It almost sounds like you are saying the only two options facing teams are the player performs up to his contract or you cut him. McKinnie had value, just not the value of his original contract. The Vikings simply weren't going to pay him for a performance well below what they were expecting. When McKinnie didn't want to do that, he was gone. Baltimore paid him and then found out what we already knew: A very talented tackle that was mailing it in on half the plays, and was overweight. He wasn't even a consistent starter with the Ravens. He kept flipping between starter and backup because of his issues with the Ravens. Is/was that kind of money worth a "part-time" tackle? We can get them at well below the price McKinnie was demanding, hence the move. PS - The Ravens defense won that Super Bowl. Ray Lewis had more to do with that than McKinnie (whom had next to nothing to do with it).
Demi wrote:
Yep. And a hell of a lot more than a HB. Which is an asset that we have. That we could possibly move to improve multiple other positions. Get in a better salary position. And likely not impact the teams on the field performance all that much. Packers won a super bowl with Brandon Jackson as their starting half back...and plenty of teams have had success without an elite "generational" back. More have had success with average running backs than with the best backs in the league.
True, and John Elway, as great as he was, lost Super Bowls until Terrell Davis enabled him to win 2 in a row. Look, I'm not saying that an MVP Running Back = Automatic Super Bowl. I'm saying that you don't take a 'step backwards' at that position unless you
have to and I don't believe that's the case. I do think you are underestimating the drop off in the rushing game (as well as indirectly affecting the passing game) if we go from Peterson to an "average back." Do you think Cassel has the talent to carry the team if we go to an "average" running attack?
Demi wrote:
They had an average rushing attack. With average rushers. In Indy the offense succeeded for years, because of Manning. Not because of Joseph Addai.
We'll agree to disagree on this one. Addai actually had some pretty good years (and some bad ones) and would have been a part of that success (He rushed for 1081 the year they won the Super Bowl). His worst year was also the Colt's worst year where they lost in the wild card round (one-and-done) with Peyton Manning under center. Before that (duing the Manning era) the Colts also had Edgerrin James and Marshal Faulk for running backs, so it's not like Manning didn't have help with a decent running attack.
Demi wrote:
Nope. Wilson isn't going to get to a super bowl with an average rushing attack and a below average defense...just like Tebow wasn't. But an elite top 3 QB like Manning? Makes Denver from a wild card team to a super bowl contender. Year in and year out.
Or...he can get s decent running back in Marshawn Lynch which only enhances his ability and makes the Seahawks offense less one-dimensional, and
win the Super Bowl. (The Seahawks were 4th in rushing in 2013)
Demi wrote:
Has nothing to do with stats. Has to do with watching him pretend to block, and passes bounce off his hands...
At least
some balls (43 anyway) didn't "bounce of his hands" if he's putting up those kind of reception yardage numbers. I think you are exaggerating here. Do you know how many passes Peterson actually drops? The answer is
here (for 2013). It's 2.5%. Even rounding up to his DISFAVOR means Peterson drops 3 of every 100 passes thrown to him. He dropped 1 of 29 passes thrown to him last year. Seems like a parroted "issue" that has no basis in actual fact.
*Edit - in 2009 he dropped 7% (4) of his passes - Full disclosure. I had only checked 2013 initially:
2007 - 10.7%
2008 - 10.3%
2009 - 7%
2010 - 10.0%
2011 - 8.7%
2012 - 5.9%
2013 - 2.5%
Still, in his worst years he dropped 1 out of 10 passes thrown to him andhe has been steadily improving since 2010... /Edit
You'll get no argument from me that blocking seems to be the weak part of his game. Zimmer has a plan to create better matchups to help Peterson succeed here. Maybe he won't succeed, but I'll wager that a better offensive strategy will yield better results. We shall soon see...