- Posts: 386
- Thank you received: 288
Wartdawg wrote:
BulldogShannon wrote: gotta disagree wartdawg. It doesn't matter who is running the ball...
Disagree? So you would have chosen to run the 159lb guy on 4th and 1 when our line couldn't block all day? You think that was the best call?
So regardless of what you think the result would have been even if Chubb was running.. you think the best decision was to run IMac? Using your fast guy theory (in traffic where his speed is negated), you think the 159lb guy was a better choice than lets say... Sony?
So.. disagree... and apparently as you see it, no runner we had could have picked it up... you think running the ball was the best decision over maybe a pass play... or maybe rolling our Eason and giving him a run pass option? I mean if no running back we had was going to be capable of picking up a yard on that play, then call me crazy... but maybe that wasn't a good play.
Saban's first year... I remember that.. they beat Vanderbilt. Saban had also inherited a 6-6 team from the previous season and dare I say they were even further away than UGA is. While they did have an inexplicable loss to UL-Monroe.. they had lost 5 players to NCAA suspension 3 weeks prior.
They also had one of the youngest OC's in D-1.. Major Applewhite, in only his 2nd year having served only 1 prior season as OC at Rice. It wasn't some seasoned veteran who was supposedly some well known guru of O.
Anyway... this isn't about Kirby for me.. so Saban comparisons don't really mean anything. Who I am railing on is Jim Chaney.. and he's been awful most of the season and was especially awful this Saturday.
Back to that Saban comparison though.. remember how I said his OC for that season was a fairly unproven Major Applewhite? Well guess who wasn't his OC in 2008; Major Applewhite.
So yes lets compare Kirby year 1 to Saban year 1... then we'll see who Kirby has as OC for year 2 as we keep the comparison going.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.