JEREMY MACLIN RELEASED?!?!?!

[Kevin5455]

After two seasons with the team, Kansas City released WR Jeremy Maclin.

http://www.espn.com/nfl/story/_/id/1952 ... wo-seasons

Thoughts?

[RevanFan]

He sucked last year. Only had one year left. So... not surprised. A little taken aback at first, but not after thinking about it.

[1312qohelet]

It was unexpected, but not really surprising.
He has had some good seasons, but he's injury prone. Couple that with his drop in production last season....cap casualty.
He could be a good pickup for a WR-needy team. Like on a 1 year "prove it" type of contract.
Low risk, with potential.

[Kevin5455]

It was unexpected, but not really surprising.
He has had some good seasons, but he's injury prone. Couple that with his drop in production last season....cap casualty.
He could be a good pickup for a WR-needy team. Like on a 1 year "prove it" type of contract.
Low risk, with potential.

I didn't know he was injury-prone.

[1312qohelet]

It was unexpected, but not really surprising.
He has had some good seasons, but he's injury prone. Couple that with his drop in production last season....cap casualty.
He could be a good pickup for a WR-needy team. Like on a 1 year "prove it" type of contract.
Low risk, with potential.

I didn't know he was injury-prone.

I believe he missed the entire season in '13 or '14 because of a torn ACL, or MCL, as well as missing several games since then with nagging injuries.

I'm not 100% sure, though....could be thinking of someone else.

[Danchat]

He sucked last year. Only had one year left. So... not surprised. A little taken aback at first, but not after thinking about it.

Maclin had 3 years left on his deal - it was a 5 year contract and he had only played 2 seasons.

I was pretty surprised by this, but I heard the Chiefs' 2018 salary cap was going to be in the negative (or very small) with the current contracts they had, so they had to cut Maclin to make room. The Ravens should think about scooping him up.

[RevanFan]

He sucked last year. Only had one year left. So... not surprised. A little taken aback at first, but not after thinking about it.

Maclin had 3 years left on his deal - it was a 5 year contract and he had only played 2 seasons.

Really? Then the article I read was very wrong.

In that case, yes this is more surprising.

[AaronS]

If the price is right I'd take him in Green Bay.

[Kevin5455]

If the price is right I'd take him in Green Bay.

http://www.espn.com/nfl/story/_/id/1953 ... sign-bills

[ultimatum77]

It was unexpected, but not really surprising.
He has had some good seasons, but he's injury prone. Couple that with his drop in production last season....cap casualty.
He could be a good pickup for a WR-needy team. Like on a 1 year "prove it" type of contract.
Low risk, with potential.

I didn't know he was injury-prone.

I believe he missed the entire season in '13 or '14 because of a torn ACL, or MCL, as well as missing several games since then with nagging injuries.

I'm not 100% sure, though....could be thinking of someone else.

Im pretty sure you're right, maclin is injury prone and inconsistent. He's definately not worth the money KC was giving him, although KC doesn't really have wr depth.....but Maclin is an average at best starter.....not a wr dynamo like a dez bryant or obj who can single handedly affect a game....even Alex Smith was suprised by this move but I think the writing is on the wall for Alex Smith this season as it will be his last in KC and probably will be replaced by game 5 or 6 this season with a rookie or another qb......smith's lack of a deep ball is holding back a very good overall KC team.....Maclin to my knowledge had only 2 very good seasons of over 1000yrds receiving. that's not elite talent that's just average starter talent.....

Rumor mill is that buffalo via lesean mccoy will be courting maclin's services.....idk if I were a team with good WR depth or needing a 3rd wr or slot guy maybe I'd sign him but no way would he be my #1 or #2 WR...the guy is just way too inconsistent/not a game breaker......