I think it is too bad that in the days of Google and the web there is no easy way to keep track of all new references to an uncommon term like that.
OK scratch the Perl example. Still standing by my point: it's a "problem" shared by many languages and it's not a problem in the first place.
"Basic" is around #9,500.
"Rust" is ~#10,950
"Java" doesn't appear at all (List goes out to 40,000) (Admittedly, somewhat biased by the dated-ness of the material, but it's still not a common one.)
Go is #106, and modern lists based on contemporary sources place it in the top 50 most used English words.
(1MB) word count list: http://norvig.com/google-books-common-words.txt
Go: 187, Basic: 759, Java: 7136, Rust: 13110
With relative frequencies 320M:103M:8.9M:3.6M ~ 100:30:3:1
http://books.google.com/ngrams/graph?content=java%2Cperl%2Cm...
I'll assume you've never knitted.
All names which the programming language is one of the last things a search engine would normally associate, but by sheer number of hits you end up finding stuff. When they were invented these names weren't good either.
The discussion about Go's name is indeed useless.
If I hear about this cool new language called Ruby and search for "Ruby Sieve of Eratosthenes," it is highly unlikely there's an article about implementing the Sieve of Eratosthenes in another language that just happens to contain the word "ruby." Conversely, the word "go" is depressingly likely to appear in articles relevant to your other search terms but unrelated to Go.
This has become less of a problem as Go has gained popularity, but in my experience it was a bigger problem for Go than it is for most languages. I search for a lot of obscure language crap out of curiosity, and I have never found an obscure language that is as hard to Google for as Go was a year ago. I know the articles existed, because I eventually found them, but dang was it hard to coax the info out of search engines.
Exactly the same applied for Go. The first four were Go-specific, and the remainder were a mix of Go-specific and pages about the Sieve with "go" somewhere on the page.
Also, as others have said, one immediately comes across references to golang everywhere.
How many search engines do you use? And which of them ignore or error on 2-letter words?
I just tried this on the only four search engines I can even think of that seemed like they MIGHT matter: google, bing, ddg, and stackoverflow's site-specific. All four obviously respected the two-letter word "go" (although for my searches only Google and SO returned results I found useful).
Second of all, I can't understand the situation where this would come up. Obviously in normal circumstances it doesn't even come up.
* You wanna search all forums at once? Use Google (or DDG, or the shitty one).
* There's a Go-specific forum? So obviously you don't need to specify Go in the search.
* The forum isn't about Go? Then why are you searching there?
So for your complaint to make sense, you need to have a particular forum you want to limit your searches to, AND you don't want to use Google with site:stupidforum.com, AND the forum covers multiple programming languages, AND the forum doesn't have a tagging system to tag go-lang posts (like basically every programming forum does), AND it has this problem I've never heard of where it rejects 2-letter words?
I'm really trying to avoid just saying "bullshit", but I think you're bullshitting us. Name one such forum.
Again, as I asked in the grandparent comment, name one search engine where you, or anyone you know personally, has had this problem.
Every time a Go article comes up, the "name searchability" discussion comes up. Go's been around for some 4-5 years now, can we all come to terms with its name?
Somehow whenever brainfuck-lang threads show up, this issue is never raised, but surely might exist just the same? What about Perl (a common word), or Basic (even more basic), heck "C" (a freakin' letter). Is that so much better for searchability? Rust -- a common word. D -- a freakin' letter. Miranda -- a language but also the name of 100s of townships, an IM client etc etc.
Go is not the first language to have this "problem", and in fair daily practice it never ever is a problem. Because you never search for Go, you search for "Go channels" or "Go image processing" or "Go GTK binding" or "Go compiler error X" etc. etc. Like you would for all these other fine examples of oddly named languages. And somehow, Google is semantically smart enough to present a few decent matches among the first 10, even with all your personalization & tracking cookies etc. etc. disabled.
So... problem? Herin lies the problem with Go? Seriously... it's just not a big freaking deal getting in the way of getting stuff done. Promised.