I simply did not believe than an American GI ever said "nuts". So, I asked my dad (WW2 veteran). He said he briefly worked for the General, and asked him what he actually wrote. The General laughed, and replied "what do you think I wrote?"
F-U
The Stars&Stripes journalists changed it to "nuts" thinking the Americans couldn't handle the profanity.
https://history.stackexchange.com/questions/40063/what-did-g...
> including by the US Army official historian
An official US Army historian's job is to make the US Army look good.
As we are all painfully aware these days, the accounts of newspapers are rarely accurate, and often outright fabrications. Why would WW2 accounts be any different?
I doubt McAuliffe would want to besmirch his record after the war, had nothing to gain by contraindicating it, and would be content to let it stand.
My father was a carefully honest man, and was never known by me to lie. He held his tongue until after McAuliffe passed away. He also told me some family secrets after all involved had passed, and asked me to keep them to myself until after he died, which I did.
It never occurred to me to ask him to write down that story, and now it's too late.
I know my evidence is hearsay and inadmissible in court. You're free to draw your own conclusions.
P.S. I was once personally involved in an incident that made the local TV news. There was nothing political about it, but each of the three local news channels got essentially all the basic facts about it wrong. But that is the "record" of the event. It pretty much soured me on the veracity of news reports.
Is it all a grand conspiracy to protect the good name and reputation of McAuliffe?
I'll say no more.
> Is it all a grand conspiracy to protect the good name and reputation of McAuliffe?
A small conspiracy is not at all far-fetched. First off, it's an inconsequential thing. Secondly, if one of the three told the truth, then he'd be called a liar by the other two. Who needs that? If you're in the military, you don't get ahead by contradicting the narrative. (My dad found that out the hard way - he was punished more than once for not writing reports that fit the narrative.)
For a grand conspiracy, consider how long Biden's staff held out insisting that Biden was sharp as a tack and writing off contrary reports as disinformation.
The most compelling bit about my evidence is the frankly laughable idea that a GI would use the word "nuts".
If there is any takeaway here, it would be that historical accounts are always suspect. History is written by the victors, as they say.
Obfuscating the context is what F's it Up. Usually that's a problematic thing, but in the case of foo and bar, the F'ed Up version is maybe better.
Germans: "Wie Sie vermutlich wissen, sind Sie und Ihre Leute von allen Seiten umstellt. Wir gehen davon aus, dass Sie bereit sind, sich zu ergeben. Bitte bestätigen Sie dies."
MCAuliffe: "Dies Nutz"
And even if not, I haven't heard anyone describe the coinage 'fupa' as offensive.
(Neglecting that there weren't many women in CS in the 1960s. I don't even see that the word-fragment would have been considered offensive in civilian context, esp. to non-US speakers of English)
Everything else is speculation unless their is some evidence that women’s complaints were the driving factor of a change in policy rather than, say, the infantilization of women or a sexist expectation that women would take exception to it.
This reads like aliens trying (and failing) to figure out why women act more like women than men do.
I think it was the opposite; they were infantilzed and sensitive, considered liable to faint or have a bout of hysteria. They were to be protected. Swearing might upset a woman.
Men had final authority over them in many cases. For example, often women couldn't get jobs without their husband's permission.
Women were sometimes the source of a sensitive, compassionate, nurting viewpoint, a balance to the man's roughness. She might appeal to him, but it was his decision.
Smug responses like this just means you don't actually have a point.
An interesting example of the quirks we carry along with us, and the fact that the combination of behavior, intention, and interpretation can mix oddly.
Everywhere else gets the shit and hell and damn that I use in regular language. No slurs and no sexual words like Fuck. But that's just good manners.
Curse words are like salt and pepper for the language. They're not necessary, but often add just the right amount of extra spice.
Honestly I don't know pussy.
I was always told that fu became foo because it lined up nicely on screens and on paper, making the code easier to scan.
foo = 1
bar = 2
looks better than fu = 1
bar = 2Hmm, "fu"? The decades confound my memory, but I don't immediately recall seeing a "fu" there? Before the "foo" of AIM-127a[1] in 1967 and MIT-LCS-TR-032[2] in 1966, there's still a decade of AI Memos, and couple of years of TRs. DSpace finds at least some "fu"s... lots of ocr fragments. The AITR-220 '64 hit is ocr fragment. My search-fu tonight wasn't up to being exhaustive (spot checks were all fragments). And also, OCR could be missing older "fu"s. But I didn't quickly find a real "fu".
A foo-bar-baz-quux in MIT-LCS-TR-365[3] in 1986.
One can start on the CSAIL collections page[4] and explore.
[1] "FOO" in abstract of AIM-127a LISP Linkage Feature: Incorporating MIDAS into PDP-6 LISP https://dspace.mit.edu/handle/1721.1/6136 [2] "Thus if FOO has the definition (LAMBDA (X Y) [alpha]), and the user calls SYSTEM1 with NAME= FOO, ADVICE= [beta], WHERE= BEFORE" on page 43 of MIT-LCS-TR-032 Pilot: A Step Towards Man-Computer Symbiosis https://dspace.mit.edu/handle/1721.1/149354 [3] "if the back trace is: FOO [1] <- BAR (2] <- BAZ [3] <- QUUX [4]" on page 20 of ID World: An Environment for the Development of a Dataflow Programs Written in ID MIT-LCS-TR-365 https://dspace.mit.edu/handle/1721.1/149633 [4] https://dspace.mit.edu/handle/1721.1/5458
The military slang 'FUBAR' f'ed up beyond all recognition, was in the student and professor engineering vocabulary. The tradition became to use 'fu' and 'bar' as nominal function names, in same manner as X and Y were nominal variables.
Often in the MIT technical reports, one would see 'x = fu(y)' or 'y > bar(z)' and so forth. If you knew, you knew.
A few years later, perhaps with the welcome progress of more female faculty and students, textbooks changed the spelling, but not the pronunciation of the vulgar acronym 'fu' to 'foo'. Again, if you knew, you knew.
And now you all know.