timmat
Member
- Joined
- Mar 12, 2014
- Messages
- 326
- Reaction score
- 0
This is not intended to be a debate thread. There have been many good points made in other threads regarding why Marshawn should be done in Seattle. So if you're inclined to make a post from that perspective, there are other "Thanks But See Ya Later" type threads available to you.
But let's see some reasons why the Hawks should consider bringing him back. Here are a few of mine:
Health - With less pounding this year and a longer off-season, Marshawn could be really fresh for next year (with the big assumption he fully heels from the surgery).
Performance - Beast still looked fierce to me. The O line was terrible at the beginning of the year when he got most of his touches. Not much any RB (or QB) can do when they are greeted in the backfield by multiple defenders as soon as you receive the ball. O line wasn't great in SB years either, but the beginning of this year took it to a new low.
Financial - Beast counts $5 mil or so against the cap next year, even if we cut him. So for a net addition of $6 mil or so, you can have Marshawn Lynch. If you cut Lynch and bring in another veteran to round out the RB corps, anyone decent will be at least $4 mill. If another veteran RB worth a salt is a consideration, it makes no sense to cut him.
Rawls - Love him. Love his attitude, nature, playing style, and of course, the results we saw. However, Lynch pounded his body for years and years before his first major injury. Rawls sustained a season-ending injury after just a handful of games. Now it would be unfair to claim that Rawls is not durable. Might have just been an unlucky situation. But Beast has come out of a zillion pileups without brakes or injury. Point is we're still not sure how durable Rawls is. We're a better team with both of them.
Play calling and Philosophy - Even during Wilson's amazing stretch of games, our run/pass splits remained consistent. If our play callers could wrap their heads around calling a game in that more open fashion even WITH Beast playing, it would be sweet. You can spread things out a bit more AND play Marshawn. Plus with more WRs ( no blocking TE) you need a stud RB pass protector. Marshawn is just that. This point requires flexibility by the OC though, so who knows there.
Kicking Butt For Another NFC Team - Do we really want to be on the hook for a $5 mill Beast cap hit AND watch him tear it up for Dallas, Arizona, SF, etc?
So, what are other good reasons to keep Beastmode?
But let's see some reasons why the Hawks should consider bringing him back. Here are a few of mine:
Health - With less pounding this year and a longer off-season, Marshawn could be really fresh for next year (with the big assumption he fully heels from the surgery).
Performance - Beast still looked fierce to me. The O line was terrible at the beginning of the year when he got most of his touches. Not much any RB (or QB) can do when they are greeted in the backfield by multiple defenders as soon as you receive the ball. O line wasn't great in SB years either, but the beginning of this year took it to a new low.
Financial - Beast counts $5 mil or so against the cap next year, even if we cut him. So for a net addition of $6 mil or so, you can have Marshawn Lynch. If you cut Lynch and bring in another veteran to round out the RB corps, anyone decent will be at least $4 mill. If another veteran RB worth a salt is a consideration, it makes no sense to cut him.
Rawls - Love him. Love his attitude, nature, playing style, and of course, the results we saw. However, Lynch pounded his body for years and years before his first major injury. Rawls sustained a season-ending injury after just a handful of games. Now it would be unfair to claim that Rawls is not durable. Might have just been an unlucky situation. But Beast has come out of a zillion pileups without brakes or injury. Point is we're still not sure how durable Rawls is. We're a better team with both of them.
Play calling and Philosophy - Even during Wilson's amazing stretch of games, our run/pass splits remained consistent. If our play callers could wrap their heads around calling a game in that more open fashion even WITH Beast playing, it would be sweet. You can spread things out a bit more AND play Marshawn. Plus with more WRs ( no blocking TE) you need a stud RB pass protector. Marshawn is just that. This point requires flexibility by the OC though, so who knows there.
Kicking Butt For Another NFC Team - Do we really want to be on the hook for a $5 mill Beast cap hit AND watch him tear it up for Dallas, Arizona, SF, etc?
So, what are other good reasons to keep Beastmode?