Jump to content
  • Hey There!

    Please register to see fewer ads and a better viewing experience:100_Emoji_42x42:

Saca312

Riot Report: The Case For Matt Kalil - Why Bringing Him Back Is A Good Idea

Recommended Posts

9 minutes ago, RumHam said:

that was a whole lot of writing that didn't prove the point. The answer is no. The only thing I learned is Williams needed a lot of help. So maybe they both need to go and we roll with moton and invest in this offensive line.

Agreed. The only sell in  point was, we are stuck with a cap hit one way or the other so we might as well keep him and since Williams wasn't as good as the all-pro honor suggests because  he had help, we can let a questionable commodity go and keep the bad known one and give him help. 

  • Beer 1

Share this post


Link to post
Share on other sites


Jordan Gross always said the job of a tackle is to lose slowly. 

 

Kalil has always lost quickly since his sophomore year. We have to keep him because it is too expensive not to, but if he is starting week 1 something went terribly wrong and a healthy Cam won't happen. 

  • Pie 2

Share this post


Link to post
Share on other sites

For a tackle, run blocking is wrestling. Pass blocking is judo.

When you're run blocking, you're trying to shove a guy out of the way. In pass blocking, more often than not you're just trying to redirect him, often using his own momentum against him.

Share this post


Link to post
Share on other sites

I think a much better & more honest title for the article would be:

"The case for Matt Kalil and why bringing him back is the least horrible  option.

Would still disagree, but makes more sense.

I can tell you as a Falcons fan, I hope they do bring Kalil back, which should tell you something. As a football fan who wants Cam to have a long career, I hope they cut him.

As I said, would still disagree, because I think that Kalil can't stay healthy and don't see any reason to expect him to play 16 games next year. The author makes the assumption that Kalil will be healthy, for no reason that I can see, except to be able to write a contrarian article.

Closing line:

"This debate shouldn’t be about whether Kalil is worth his salary, but rather whether he is worth the $7.25m they will save by cutting him – and who the starting tackles will be next year will be if he’s gone."

 

Naah, Kalil has been so bad and so injured since his rookie year that the only reason you would keep him is because you don't want 14 mil of dead money on your cap over the next two years. You can't possibly expect him to be part of an effective OLine for 16 games.

You're better off drafting the best OT at 16, putting him  at LT and protecting him with lots of quick passes, an extra lineman, and TD/RB help than relying on Kalil. 

  • Pie 2
  • Beer 1

Share this post


Link to post
Share on other sites

I do agree with the premise that the question should be whether or not Kalil's is worth $7.25M to us.

It's just that my answer is "Hell fuging no!" He's subpar when available and rarely available. That's not worth $7.25M. If I thought he'd be healthy for the entire season then I'd probably bring him back. Sadly, subpar starting LT play is worth $7.25M. $7.25M would rank 20th among LTs.

Edited by LinvilleGorge
  • Pie 1

Share this post


Link to post
Share on other sites
On 2/28/2019 at 5:53 PM, Untouchable said:

I think that's the point being highlighted in the article. It was schemed that way to help Williams hide on the play. Then he doesn't do well with his technique on the play anyway.

They also left Kalil on an island on that play as they did all too frequently. You have to ask yourself why would a team with Matt Kalil as thier tackle be leaving him alone on an island? .... Like ever.... 

 

There are some here on the Huddle who would be willing to chip in and buy an island for Kalil and leave him on it... forever

  • Pie 1
  • Beer 1

Share this post


Link to post
Share on other sites
On 3/1/2019 at 9:18 AM, Jeremy Igo said:

Jordan Gross always said the job of a tackle is to lose slowly. 

 

Kalil has always lost quickly since his sophomore year. We have to keep him because it is too expensive not to, but if he is starting week 1 something went terribly wrong and a healthy Cam won't happen. 

I’m a bit ashamed that you are falling for the too expensive to not keep him. Look at @LinvilleGorge‘s post above. I just don’t know why it is too hard to understand that we have $15m in dead cap for him whether he is here this year or not. Let’s put that away because it doesn’t matter. We used bonuses to lower his first two year’s cap numbers by $15m. That is lost money and there is no way to avoid it. The whole point of using a post June 1st cut is to make that cost easier to swallow over two years.

There is however a decision on his 2019 salary of $7m+. I can’t see how you can say what you did and honestly say that it’s too expensive to not keep him. No, that’s wrong. There’s $7m+ reasons to say he’s way too expensive to keep.

Edited by stbugs
  • Pie 1
  • Beer 2

Share this post


Link to post
Share on other sites

Everyone worried about the dead space by cutting him. Well how about keeping a dead player? Because that's exactly what he is. Why keep a player around who does absolutely nothing, not even good for depth, while having to sacrifice someone else who has busted his ass to make the team?

Edited by KillerKat
  • Pie 1

Share this post


Link to post
Share on other sites

He's a waste of money and a waste of a roster spot. Those are two distinct things.

If we cut him, then he's just a waste of money. If we keep him, he's both. He's not someone we need to keep nor is he someone that we should ever let see the field again. 

Don't buy into the "better the devil you know" talk, because the devil we know is a massive liability. We don't have a chance.

At least if we tried to replace him we'd have a chance at getting better.

  • Pie 2
  • Beer 1

Share this post


Link to post
Share on other sites
1 hour ago, stbugs said:

I’m a bit ashamed that you are falling for the too expensive to not keep him. Look at @LinvilleGorge‘s post above. I just don’t know why it is too hard to understand that we have $15m in dead cap for him whether he is here this year or not. Let’s put that away because it doesn’t matter. We used bonuses to lower his first two year’s cap numbers by $15m. That is lost money and there is no way to avoid it. The whole point of using a post June 1st cut is to make that cost easier to swallow over two years.

There is however a decision on his 2019 salary of $7m+. I can’t see how you can say what you did and honestly say that it’s too expensive to not keep him. No, that’s wrong. There’s $7m+ reasons to say he’s way too expensive to keep.

Not going to lie. I felt ashamed as well. I got into it big-time with CAtcrapreader head guy and others, and couldn’t believe he actually ran a website with his perceived knowledge. Now Jeremy joins in? Say it ain’t so. 

Share this post


Link to post
Share on other sites

Bringing Matt back would confirm the obvious,...

the Dumbass Disease has no paycheck bias— 

 

Share this post


Link to post
Share on other sites

Looking at the math on overthecap, I don't think it makes any sense to keep him. A post-june 1st cut saves us 7.25 million this year with a 9.8 million dead cap next year. If we cut him next year, we still have a 9.8 million dead cap. So the question is do you think you can replace his potential production for 7.25 million? Seeing as how we brought in Chris Clark on a minimum salary and didn't really notice a difference, I think that's a safe bet. 

  • Pie 2
  • Beer 1

Share this post


Link to post
Share on other sites

Williams looked pretty damn good against Demarcus Lawrence with a bum knee before Lawrence took out what was left of his knee. 

For the little sample size it was, the Moton Williams combo was the best I had seen the Panthers line in a long time and it was against a very good Dallas defensive line.

There is a better chance of Williams staying healthy than Kalil so that should make the decision pretty easy in my mind.

  • Pie 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×