James Starks is one of the most intriguing and frustrating talents the Green Bay Packers have drafted in years. After a monster postseason in 2010 with 315 yards en route to a Lombardi Trophy, Packers fans thought they had found their guy.
Unfortunately for them, Starks reverted back to what he was before the magical postseason and got injured.
Three years later we face the same question.
Starks came in for the injured Eddie Lacy in the Washington Redskins game and went off for 132 yards on only 20 carries with a touchdown. All of the sudden he is in our hearts again, pulling at us to love and trust him.
And then the seemingly inevitable occurred.
Starks was energizing the running game with 55 yards on 14 carries at Cincinnati and then went down. Across the country, Packers fans rolled their eyes and sighed. We knew it was coming, but why did he have to break our hearts with such a game?
Starks is a great talent. He can also be classified as injury-prone. Don’t get me wrong, I think he could be something special, but it does not seem that he is worth the risk anymore.
With the young guard of Eddie Lacy and Johnathan Franklin (who showed his stuff after Starks went down), Starks just does not have a place on the roster. The Green Bay Packers cannot depend on him, and unfortunately this injury may mark the beginning of the end of his time in Green Bay.