What is the straight answer for this question: Why is the language
named as "Go"?
-ganesh
There is no single answer. It's a nice short name that can evoke a number of different ideas.
-rob
"Go" could the first step toward the next, better, multicore language,
which presumable could be called "There".
If "Go" fails to catch on, or quickly becomes obsolete, it could then be
called "Gone".
Of course, one factor that may drive it in this direction would be the
failure of the future "Ogle" debugger to usefully expose interactions
across multiple goroutines, in which case the debugger could become
"Boggle" ("to startle with amazement or fear").
If "Go" turns out to be a language design that takes us in the wrong
direction, we could always create the language "Return" or "Come" to get
back. Or, if "Go" was a complete mistake, we could rename it "No-Go" as
a reminder.
I suppose that's an inherent problem when using a verb to name a
language. Letters (B, C, D, R, etc.), acronyms (BCPL, APL, PLM, etc.)
and nouns (Python, Ruby, Occam, Java, etc.) are much harder to have fun
with.
And "Go" is certainly fun!
-BobC
--
Samuel Baldwin - logik.li
Od (or od) would not be a good name - it is a venerable Unix command,
and its existence caused the Bourne shell to handle loops differently
from if and case statements:
if ... fi
case ... esac
do ... done
Because the Algol-like notation should have used 'do .. od' for
consistency, but couldn't because the 'od' command already existed.
Using a name that is a partially upshifted version of a standard
command is not a good idea either - it causes problems on case-
insensitive systems such as MacOS X (and Windows).
--
Jonathan Leffler