Merged Pearl Harbor: "Revisionists" vs. "Traditionalists"

I'll bring it flowers and chocolate.

Seriously, I hope to work my way down to those papers this week. -ish.

Not to worry if Bob comes back we'll confuse him with questions on why the Japanese declaration of war wasn't sufficient reason for the US to declare war in turn......
 
The same can be said for archaeologists. I remember a memorable fist fight amongst archaeologist in Cyprus over the consolidation of pottery nomenclature into one list
Shades od the Bone Wars.

No Swiftian comments allowed, being a centre breaker myself
My first thought was Instruction Sets.........
:boxedin:
 
My first thought was Instruction Sets.........
:boxedin:

I flashed on my experience with trying to send multi-byte values between very different systems- how the ******* **** did my 1001 test value turn into 38848, or sometimes 59651?

Writing my own custom code to reverse the bit-order of bytes, or reverse the byte-order of longer types - ooohhhh, if "Endian" isn't a fighting word, then programming simply isn't worth fighting over!
 
I flashed on my experience with trying to send multi-byte values between very different systems- how the ******* **** did my 1001 test value turn into 38848, or sometimes 59651?

Writing my own custom code to reverse the bit-order of bytes, or reverse the byte-order of longer types - ooohhhh, if "Endian" isn't a fighting word, then programming simply isn't worth fighting over!

If we're getting into programming wars, there is one fight to rule them all: Emacs vs. VI.
 
Not to worry if Bob comes back we'll confuse him with questions on why the Japanese declaration of war wasn't sufficient reason for the US to declare war in turn......

And for fun we'll point out that the declaration was written AFTER Gaimudaijin learned that the attack on Pearl had been successful. I wonder what would have happened if it had failed utterly? Would they have ignored the PI like Bob seems compelled to do? :D
 
I'd guess she was using assembler, if not straight machine code.
Fortran and Cobol were still waiting for the 50's
 
ISTR seeing programming forms that had columns labeled with operand field names for various instructions. I just don't remember where, or what computer it was for.

In my youth, I ran a phototypesetter that needed to have its paper tape loader keyed in from the front panel. I think that was a PDP-8 in drag. I never did any programming on it, though.
 
I'd guess she was using assembler, if not straight machine code.
Fortran and Cobol were still waiting for the 50's
As far as my mom is concerned, COBOL is still waiting for the 50's ;)

(AFAIK she's been coding that crap since the 70's).
 
One Internet to the person who can name the programming language Grace Hopper used during the war.
I'd go with machine code too, the Mark 1 was a electromechanical device.
IIRC her work on compilers was late, early '50s.
 
Look, it's pretty clear what really happened: the U.S. let the Japanese successfully attack Pearl Harbor. The Japanese found out about this, felt bad about winning an unfair fight. So in return they let the U.S. win at Midway to balance the scales. (I mean, really, how else can one plausibly explain how the Japanese lost that battle? Letting a critical search plane be delayed for thirty minutes while the rest are all sent off on schedule? Needing a second strike to knock out Midway's airfield? A search plane which finds the U.S. carriers but which then has a radio failure? Loading, unloading, and loading aircraft for an anti-ship strike? Clearly, such actions can only be explained by Japanese complicity to deliberately lose the battle, thus giving the U.S. a "false" victory like the one the Japanese had at Pearl Harbor. It's blindingly obvious, I tell ya!)
 
Last edited:

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom