Quote:
|
Quote:
Clearly there's bias involved in reporting. |
Quote:
|
Quote:
Orton was only sacked once in 3 games. That proves quite a bit. |
Quote:
|
Orton isnt Elite, but he showed us what our team could be with an above average quarterback. See week 14.
How you dont pay him and keep him here is beyond me. |
Quote:
|
Quote:
|
Quote:
He knew this was Cassel's team and probably wasn't going to be given a fair shot at a starting gig. So he bolted for Dallas. |
Quote:
he gave us a glimpse of what a QB that can get the ball downfield would do for the Chiefs. |
I am curious to know why Orton was quick sign with Dallas without visiting any other teams.
|
Quote:
|
Quote:
I don't know if Orton cared about starting. Clearly here was his best chance at starting. Even if Cassel was named the starter, if he sucked the first few weeks, there would be enormous pressure to start Orton. In Dallas, Romo could go the first 6 weeks 2-4 with 3 TDs and 10 INTs and they likely wouldn't switch. |
Quote:
|
Quote:
When Orton came in, Haley had been fired and Crennel allowed Muir to simply call the plays he chose without running them by him first. Orton got to the line with ample time to make pre-snap reads, a luxury not afforded to Cassel often last season. With the information he was able to gather, he could identify favorable matchups, hot routes, blitzes, and call for a change in blocking assignments accordingly. That, in and of itself, would be a huge plus as far as sacks go. The difference is, even with all the extra info from pre-snap reads, Orton still couldn't punch it into the endzone. |
All times are GMT -6. The time now is 04:49 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.