KCKingdom
Fansided

Kansas City Chiefs: 10 likes and 10 dislikes from win vs Texans in week 1

KANSAS CITY, MISSOURI - SEPTEMBER 10: Patrick Mahomes #15 of the Kansas City Chiefs and Deshaun Watson #4 of the Houston Texans shake hands before the start of a game at Arrowhead Stadium on September 10, 2020 in Kansas City, Missouri. (Photo by Jamie Squire/Getty Images)
KANSAS CITY, MISSOURI - SEPTEMBER 10: Patrick Mahomes #15 of the Kansas City Chiefs and Deshaun Watson #4 of the Houston Texans shake hands before the start of a game at Arrowhead Stadium on September 10, 2020 in Kansas City, Missouri. (Photo by Jamie Squire/Getty Images) /
facebooktwitterreddit
Prev
4 of 4
Next
Kansas City Chiefs
Deshaun Watson #4 of the Houston Texans scrambles against the Kansas City Chiefs (Photo by Jamie Squire/Getty Images) /

6. Easy Peasy, Touchdown Squeezy

On Houston’s first touchdown drive of the game, they marched 80 yards on just nine plays, making the Chiefs defense look rather silly. Or, at least, incompetent.

Watson completed all five of his pass attempts on the drive for 53 yards while David Johnson ended the drive with a 19-yard rushing touchdown. Speaking of which…

7. Rewind to 2016

David Johnson looked pretty good in his first game as a Houston Texan. He ran the ball only 11 times, but collected a whopping 77 yards and scored the aforementioned touchdown. He also caught three passes for 32 yards, giving him 109 total yards of offense for the night. He looked good, maybe putting him on the path to return to his 2016 glory days.

This is a dislike because he’s not a Chiefs player, obvs.

8. Wiper Blades Needed

Love Andy Reid and loved his visor, but how could he see out of that thing?

9. A Lacking Trio

Unsurprising, but disappointing and concerning numbers from PFF:

10. The Controversy

Alright, time to get a little serious.

Before last night’s game, the Chiefs and Texans locked arms in unity in a moment of silence for equality and Black Lives Matter. During this time, undoubtedly, boos were heard from the small crowd inside Arrowhead Stadium.

Most people, especially on Twitter, took this to mean that the Kansas City fans were booing the moment of unity. Those same people, which includes local politicians to sports writers to news anchors, immediately condemned those fans.

Before I go any farther, let me be clear: those booing the moment of unity between the two teams were wrong, and those defending booing the moment were also wrong.

Yet, I don’t think that was the case. At least, not entirely. It appeared to be more of a grey area, and sure, I get why people like to deal just in cases of black-and-white. It’s a lot easier than dealing with nuanced situations. The case of the booing, though, falls directly in that grey area, where most issues reside.

From text conversations and other messages with friends who were at the game, plus through videos posted from those at the game, and from quotes from the players and coaches on the field, it appears that the fans weren’t booing the moment of unity but were instead booing the Houston Texans, the opponent of the Kansas City Chiefs, as they took the field.

Go ahead and attack me if you so choose. That already happened on Twitter last night, and I had a family member post on her Instagram story that anyone trying to rationalize the booing is, and I quote, a clown.

So I can take it.

What I can’t exactly take is people attacking Kansas City, my city, calling the residents things like bigots, when the full story isn’t known.

Will it ever be known? No, probably not. In any case, the boos of a few aren’t reflection on a city as a whole. Things were blown out of proportion last night by several outlets.

The City of Kansas City, Missouri, is a great place with great people. Does it have its flaws? Sure. Every city does. But don’t let those on Twitter choose what you think. Dig for yourself.

From what I’ve found, the fans were booing the opponent, not a moment seeking equality.

Next. 3 Star Performances vs Texans in Week 1. dark