You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Which is to say, the idea that the cities were warned doesn't even make much sense of the face of it. It's not something that Groves, Truman, Tibbets, or anyone else connected to the bombing program ever claimed. So why are do so many people claim it today?
The answer is pretty clear to me: they think it lessens the moral difficulty of defending the bombing. If we warned them, and they didn't surrender or evacuate, then it's really their fault they died, not ours, right?
This is bad reasoning on every front. If Bin Laden had said, "I'm going to attack major American cities," and then he did it — would we have said, "well, he warned us"? No, of course not. It's an absurd notion. Even if the warning was very specific, it still doesn't absolve.
The fact that there was no warning in the case of Hiroshima/Nagasaki just makes this argument all the more ridiculous. It'd bad reasoning even if it HAD happened — but it DIDN'T happen. Which makes it something of a farce.
I always tell people who spout this: look, one CAN make arguments in favor of the Hiroshima bombing (and Nagasaki, too, but it gets harder). All arguments for and against are contentious, but they can be made. But don't base your argument on something that 100% didn't happen!
(And before people get on me: I know there are other myths/spin/lies/misconceptions, including big ones. But this is the one that bugs me the most, because it 100% didn't happen. There's no real room for interpretive dispute here — it's just false.) /THREAD
I meant to add this, too, but work internet went down: I've written all this up before, some time back. The psychological warfare document from 1946 is linked in the post as a PDF; I got it from the Manhattan Project files in the National Archives. See:http://blog.nuclearsecrecy.com/2013/04/26/a-day-too-late/ …
There you go. That’s hitting the nail on the head.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
