- Posts: 3930
- Thank you received: 3262
Please Log in to join the conversation.
thriller wrote:
1. Who had more at stake in the SECCG, Bama or Georgia? Answer: Bama BY FAR. Lose and GO HOME (er - to a New Year's Day bowl game). For Georgia, lose and just be playing someone else in the CFP.
thriller wrote: 2. What was the potential DOWNSIDE of a Bama win for Bama, versus a Georgia win for Georgia? I was a little confused by the question. As he explained, Bama had ALL CHIPS IN THE MIDDLE OF THE TABLE. What happened to Metchie shows you the potential DOWNSIDE of being in Bama's position. Georgia sure didn't want THAT. In other words, the risk for Bama in giving it EVERYTHING was getting a star like Metchie injured, but the win made the "sacrifice" "worth it".
thriller wrote: 3. Seven of Bama's points in the SECCG came on a pick 6. If Stumpy Stetson had thrown to the CORRECT receiver on that play (Jermaine Burton, on the outside - had his man badly beaten), it would have been 6 points the OTHER WAY. That's a 14 point turnaround. It was "only" a 17 point final margin.
thriller wrote: 4. The OTHER INT in the game was not The Hobbit's fault - something I hate to admit is true. It was, of all people, Brock Bower's fault for inexplicably stopping on his route - AT THE ALABAMA 10 FREAKING YARD LINE. There's 7 more points, right there.
thriller wrote: 5. And finally, as he pointed out to me, Georgia's win over Michigan was much more impressive than Bama's win over Cincy, like it or not. Sure, Bama beat a double digit spread, but Georgia SLAUGHTERED a 7.5 point spread. Even casinos that had Georgia as 10 point favorites were shocked at how easy that was. The eye test means a lot to gamblers.
So, according to Bob, Bama's win in the SECCG is actually just keeping the spread DOWN. (Some think the REAL spread should be closer to 7.5, which he thinks is why the spread has actually gone up slightly.)
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.