Kansas City Chiefs: Pros and cons of cutting Jeremy Maclin

6 of 6

Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: Richard Mackson-USA TODAY Sports /

This isn’t a fun time for KC Chiefs fans right now, but we’ve made it through the days when Donnie Avery and Steve Breaston were starting receivers for the team. We’ll get through this together.

More from Kansas City Chiefs

When the Kansas City Chiefs signed Jeremy Maclin two years ago, I was psyched! I couldn’t wait to watch a former MU great come into Arrowhead and explode into the end zone week after week. That was cut short for everyone though and now we have to roll with Chris Conley and company.

While this move doesn’t make sense for us as fans, the Chiefs did what they felt was best for the team. Maybe they’ve seen vast improvements in Conley and think that Robinson will take a major step in year two, but I’m worried about this offense.

The Chiefs offense struggled badly in 2016 and that was WITH Maclin in town. I get he had a down year, but taking him out of the equation certainly doesn’t help any. This could be an ugly season for the KC offense.

It’s also not cool how a large majority of the Chiefs organization attended Maclin’s wedding, waited two weeks into OTAs to cut him, and then threw him out like garbage. They’re not treating their players very well and that’s problematic. Not a good way to convince future free agents to come here.

Next: Ten Options to Replace Jeremy Maclin

I’ll leave you all with this: The other day I was sorting through my closet and found my Maclin shirsey. I don’t even know what to do with it now. Do I keep it? Do I throw it away? Do I chuck it at someone passing by my apartment window? Do I check it down to the closest receiver? Any help would be appreciated.

Home/Kansas City Chiefs