![]() |
Quote:
When the pick was made, it was panned by many as a stupid luxury pick for a team that had pressing issues at NT, LB, QB and yes, WR. Instead we took a gimmicky scat-back that likely couldn't stay healthy who would struggle to find a regular role in the offense. We were informed that he was clearly going to be the #3 WR the team desperately needed (and that someone like Benn or Williams would be nowhere near as good as the elusive midget). 16 NFL regular season games and 1 post-season game later he has shown to be a guy that couldn't stay healthy and who we couldn't find a regular role in the offense. It also appears increasingly likely that he isn't going to be the #3 WR and most assuredly won't be better than most of the WRs taken after him. It's not a knee-jerk reaction, it's a vindication. Those of us that hated this pick from the moment it was made have been right across the board. If you need to call it a knee-jerk reaction in order to make yourself feel better, so be it. But there's nothing knee-jerk about this; the angst over this pick has been a long time coming. |
Quote:
|
Quote:
Meaning he will be getting plenty of carries. And just because a guy is labeled 3rd down back doesn't mean he actually comes in on 3rd down. 3rd down back is such a mislabled term. Look, If he fails, fine. I'll eat crow. But i'm not going to sit here and write the kid off before he even gets a chance like some of you want too. That's irrational. He showed flashes last season that he can be explosive. Lets see what he can do before we start bitching about him. |
Quote:
|
Quote:
Sounds like an O-line that failed when we needed it. |
Quote:
That 4th and inches was a John Cooper move. I think their short yardage issues start upfront continue at the RB position and end with the coaching staff. |
Quote:
|
Broke into little pieces by week 8.
|
Quote:
We're still looking at getting a LBer with our 1st rounder who's not likely to be better than Washington out of TCU who was another guy we should've considered. Oh yeah, and that doesn't even get into the myriad of WRs that would've been great pickups for us last season at that spot that we passed on. Yeah, I'd say that's a disaster. When you look at not only what he's been and where we took him, but also what the opportunity cost was in a very very deep draft, that pick has been a complete mess. |
Quote:
He made a 240 pound FB miss on a wet field, took advantage of piss-poor ST coverage and returned a punt for a TD. He scored against SF after a LB took a shitty angle and whiffed. No one else was even in the area for the next 25 yards. Those are the two biggest "plays" he made all year. |
I'd like to see EXACTLY how DMc is used this year before I vag out over all of this.
|
Quote:
I love this crap...first it was Hootie saying it...now it's you.... McCluster might be able to take 5 or 6 carries a game without getting his ass destroyed and fumbling all over the place. That's less than 100 carries a year, and that's if he stays healthy for ALL 16 games. The Chiefs ran the ball 556 times last year. Who is going to carry the ball the other 456 times? Not Charles. Let's say he gets 300 of those carries. So you're left with another 156 carries. Those go to your #2 running back. And if your #2 running back is, you know, actually a good player, why would you want to take carries away from him and give them to a guy who can't even run between the tackles without getting destroyed? McCluster is going to catch 30 passes for 300 yards out of the backfield next year and look exciting as **** doing it... |
Quote:
|
Quote:
Smells like draft season..... |
The "I was right all along" argument is so ****ing shallow. I guess that's a good thing or half this board would have drown.
|
All times are GMT -6. The time now is 10:16 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.