Five More: Packers 55, Bears 14
I’m a little slow on this today, but that will happen when you have to catch a morning flight from Milwaukee to Los Angeles on the day after the Green Bay Packers play on Sunday Night Football.
But, wifi, you say? Apparently, Southwest’s in-flight wifi doesn’t work for anyone who’s actually trying to do work. But hey, at least the asshole next to me got to watch a bunch of episodes of Deadliest Catch!
Southwest — where jerkoffs can suck up all the Internet bandwidth with their free TV, but anyone who actually has shit to do can go fuck themselves!
Anyway, speaking of people who can go fuck themselves — the Chicago Bears. They do indeed still suck.
Here are five more thoughts on that beat down.
Quality of opponent
Before anyone goes and books a room for the Super Bowl in Arizona, let’s take note of just who the Packers beat on Sunday night. A Chicago Bears team that is obviously just bad. Yeah, they’ve got some offensive firepower, but their defense is awful and when you spot your opponent 14 points, some of your offensive game plan goes out the window. This isn’t to say what the Packers did on Sunday night wasn’t impressive. It was. That being said, here’s a Bears team that’s given up 50-plus points two games in a row. That hasn’t happened since the Rochester something or others did it back in 19whogivesafuck. In other words, this Bears team is historically bad.
All hands on deck
Much was made all week about how guards T.J. Lang and Josh Sitton might not be able to go. Then safety Morgan Burnett was downgraded from probable to questionable late in the week. And of course, all three of those guys started. Burnett had six tackles and a sack. He also knocked down a pass. Sitton and Lang made us forget they were in there, which backups Lane Taylor and J.C. Tretter probably would not have done. So, much ado about nothing.
That no punting streak lasted for a while
Remember the last time the Packers and Bears met? No punts. There were no punts by the Packers in the first half of Sunday’s game either. They were too busy scoring at will. The Packers ended up punting three times and the Bears punted four. Most those punts came when the game was already over. In two games this season, the teams have a combined seven punts. That’s pretty amazing.
That backup quarterback job…
We’ve seen it before this season. That is, Matt Flynn getting playing time. On Sunday night, Flynn entered the game in the third quarter. It’s not as if the Packers were going to fling it around with a 40-plus-point lead, but they did attempt some passes. And like each time previously this season, Flynn has looked less than impressive. On Sunday, he was 1-of-5 for 4 yards. Sure, Flynn hasn’t gotten time when the games mean anything this year, but all the more reason he should be looking better than he does. Here are some of Flynn’s numbers for the season: 38.5 completion percentage, 2.6 yard average, 14.6 rating, zero touchdowns and one interception. So when can we just turn this job over to Scooter Tolzien? I mean, it’s nearly impossible to put up worse numbers than Flynn’s.
Tight ends, huh?
I read something earlier today about how the Packers finally got the tight ends involved. Uhhhhhh…. really? Yes, both Brandon Bostick and Andrew Quarless caught touchdown passes, but that’s the only noteworthy thing that happened. Here’s the state line: 5 receptions, 17 yards. Woooooooooo! Oh, and that’s for all three of the Packers’ tight ends combined. Really tore it the fuck up, huh?! Here’s the breakdown. Andrew Quarless: 2 catches, 10 yards; Richard Rodgers: 2 catches, 6 yards; Brandon Bostick: 1 catch, 1 yard. I will grant you, the Packers do seem to look for the tight end in the end zone, but by and large, these guys are either not part of the game plan or just plain incompetent.