Shortly after Joint Chiefs of Staff General Mark Milley defended the military teaching critical race theory, Marine veteran J.D. Vance took to Twitter to air his grievances with Milley's take.
Instead of focusing on woke politics, Vance made the argument that the Joint Chiefs should be focused on winning wars, not on advancing progressive politics.
"I personally would like American generals to read less about 'white rage' (whatever that is) and more about 'not losing wars,'" Vance tweeted.
"What I find so enraging about the Joint Chiefs’s pandering on progressive wokeness is that they know damn well the geography and politics of who dies in American wars," he wrote in a Twitter thread. "The conservative Americans you trash are disproportionately bleeding for this country."
"I’m glad you got your viral clip, General. Maybe you should try defending the enlisted folks, their families, and their values," he concluded.
Interestingly enough, Deadspin journalist Julie DiCaro attempted to dunk on Vance for "never serv[ing]" in the military.
"Guys who have never served calling the US Military 'losers' is a bold strategy, Cotton. Let's see if it pays off," she tweeted.
DiCaro was too busy going to bat for Milley and critical race theory that she missed one rather important point: Vance is a Marine veteran who was stationed in Iraq during his service between 2003 and 2007.
A simple Google search serves as proof.
Join and support independent free thinkers!
We’re independent and can’t be cancelled. The establishment media is increasingly dedicated to divisive cancel culture, corporate wokeism, and political correctness, all while covering up corruption from the corridors of power. The need for fact-based journalism and thoughtful analysis has never been greater. When you support The Post Millennial, you support freedom of the press at a time when it's under direct attack. Join the ranks of independent, free thinkers by supporting us today for as little as $1.
Remind me next month
To find out what personal data we collect and how we use it, please visit our Privacy Policy