RFC 3092 - Etymology of "Foo" (2001)
tools.ietf.org
tools.ietf.org
Their use of foo, bar and foobar without explanation was extremely confusing to me and made the whole book very difficult to understand for me as my brain constantly wasted brain cycles on trying to understand these words in the code samples.
Of course it didn't help that back then my English was practically not existent yet.
It's funny how these completely made-up words have become real jargon one has to know when working in this industry, to the point where at least for me personally, not knowing them was a huge barrier to understanding a basic book about our profession
(I might also just have been too young yet. I remember reading the chapter about regexes (littered with foobar) and thinking "nobody in their right mind can find this useful for anything")
RFC 3092 - Etymology of "Foo" (2001) (ietf.org)
The 2001 in the title really should be 1 April 2001, lest someone thinks this RFC is otherwise notable in some way. Angostura 15 minutes ago | link | parent | flag
Why? It's not a prank.
I sense that you have a future in marketing [1].[1] http://en.wikipedia.org/wiki/April_Fools'_Day_Request_for_Co...
Comments like "xyz is easier" forget that we aren't all the same.
Foobar applies to most of my code.
example: 胖胖 (pàng pàng) "fat fat," nickname for a fat child in the class (generally considered a compliment.)
Chinese speakers are also (according to my teacher) very fond of the English "Bye Bye" for goodbye, since it follows the same pattern, and will use it in place of 再见 (zài jiàn) "again see" if they know you will understand it.
Amusingly, Polish uses pa for goodbye (not infrequently doubled up) and tata for father.