The EU

Google says the EU requires a notice of cookie use (by Google) and says they have posted a notice. I don't see it. If cookies bother you, go elsewhere. If the EU bothers you, emigrate. If you live outside the EU, don't go there.

Sunday, April 17, 2016

Saying What You Mean

For John, BLUFPlain speaking is good.  Nothing to see here; just move along.

This is the on-line publication Tom Dispatch, with an article by Retired Air Force Lt Col William Astore, "Tomgram: William Astore, Words About War Matter".

The article starts out like this.  It has a snarky tone, but it is mostly correct.

At the moment, there are a maximum of 3,870 U.S. military personnel (or 7,740 actual boots on the ground) in Iraq supporting the war against the Islamic State. That’s the “official cap” imposed by the Obama administration, because everyone knows that the president and his top officials are eager to end American wars in the Middle East, not expand them. Of course, that number doesn’t include the other 1,130 American military types (or 2,260 boots) -- give or take we don’t know how many -- who just happen to be there on what’s called... er, um... “temporary deployments,” or are the result of overlap from rotating deployments, but add up to perhaps 5,000 trainers and advisers, or maybe, for all we know, more, including 200 Special Operations forces whose numbers are officially acknowledged by no one but mentioned in press reports. And naturally that 5,000 figure doesn’t include the American private contractors also flowing into Iraq in growing numbers to support the U.S. military because everyone knows that they aren’t either troops or boots on the ground and so don’t get counted. Those are the rules.

Do keep in mind that this time around the whole American on-the-ground operation couldn’t be more limited. Though the numbers of U.S. trainers, advisers, and Special Ops types continue to creep up, they are, at least, helping the Iraqi military reconstitute itself on Iraqi bases. In other words, this round of Washington's Iraq wars bears no relation to the last one (2003-2011), when the Pentagon had its private contractors build hundreds of U.S. bases, ranging in size from American towns to tiny combat outposts. This time, the U.S. military has no bases of its own, not a single one... er, um... at least it didn’t until recently when an American Marine, a specialist in firing field artillery, died in an Islamic State rocket attack on what turned out to be an all-American Marine outpost, Fire Base Bell, in the northern part of the country. The artillery operations he was involved in supporting the Iraqi army in its (stalled) drive on the country’s second largest city, Mosul, are not, however, “combat operations” because it's well established that no American troops, Special Ops units possibly excepted, are in combat in that country (or Syria). In fact, U.S. officials point out that artillery doesn’t really count as combat. It’s more like U.S. air operations against the Islamic State except... er, um... it takes place on the ground.

Language is important and to the degree we distort the language, to that degree do we deceive ourselves as to what is going on around us.  I touched on this in a recent post.

There is one place that the author seems to go off the rails.  This is when he pointed out that we spend billions on weapons system that may or may not be appropriate to the guerre du jour, and then pointed out the cost effectiveness of "the 9/11 attacks on American soil were estimated to have cost Osama bin Laden at most a half-million dollars.”

Is Lt Col Astore advocating we go back to using dumb bombs and just laying waste to various Arab/Muslim cultural buildups, including towns and cities?  I would hope not.  Our kind of warfighting does cost more because (1) we do it over there and (2) we actually try to discriminate between combatants and non-combatants, even if we fail a lot.  We try.

Regards  —  Cliff

No comments: