Golang Diaries I
tbray.org
Golang Diaries I
1–10 of 79 posts
Re: Golang Diaries I
#2"After a few painful instances of searching for things like “go array literals” and “go repl” I got into the habit of sticking with Golang; and so will this diary."
https://encrypted.google.com/#q=go+array+literals
https://encrypted.google.com/#q=go+repl
...
Re: Golang Diaries I
#3>First, the name. “Go” has too many meanings and is among the world’s lousiest Google search disambiguators.
Enough with this old wives tale. Yes, "Go" is too generic. Nevertheless, Google understands it just fine. Case in point:
>"After a few painful instances of searching for things like “go array literals” and “go repl” I got into the habit of sticking with Golang; and so will this diary.
Both his examples ("go array literals" and "go repl") return a page full of Go related results (the documentation, the golang-nuts discussion list, related blog posts, etc).
What exactly is painful about it?
Re: Golang Diaries I
#4> First, the name. “Go” has too many meanings and is among the world’s lousiest Google search disambiguators. Enough with this old wives tale. Yes, "Go" is too generic. Nevertheless, Google understands it just fine. Case in point: > "After a few painful instances of searching for things like “go array literals” and “go repl” I got into the habit of sticking with Golang; and so will this diary. Both his examples ("go…
Perhaps these examples weren't the best. When searching for more general things it helps to put in golang. For example "Running go on multiple machines" or "Running go on multiple cores":
https://www.google.co.uk/search?q=running+go+on+multiple+mac...
vs
https://www.google.co.uk/search?q=running+golang+on+multiple...
Re: Golang Diaries I
#5"Nice C-flavored code (there’s even ++) but look, Ma, no semicolons!"
The hate for semicolons is far, far more annoying to me than semicolons ever are.
Re: Golang Diaries I
#6Golang ins't all that new. I don't get it why so many articles exploring the basics get so much spotlight.
It's a good language. I'd like to see more articles about things made with it and not about it.
Re: Golang Diaries I
#7> First, the name. “Go” has too many meanings and is among the world’s lousiest Google search disambiguators. Enough with this old wives tale. Yes, "Go" is too generic. Nevertheless, Google understands it just fine. Case in point: > "After a few painful instances of searching for things like “go array literals” and “go repl” I got into the habit of sticking with Golang; and so will this diary. Both his examples ("go…
The filter bubble! After you've googled enough, google starts knowing what domain you are searching in.
If you search for 'array literals' you'll likely get Go results at the top rather than, say, Javascript (which is what I get, I just tried).
Re: Golang Diaries I
#8> First, the name. “Go” has too many meanings and is among the world’s lousiest Google search disambiguators. Enough with this old wives tale. Yes, "Go" is too generic. Nevertheless, Google understands it just fine. Case in point: > "After a few painful instances of searching for things like “go array literals” and “go repl” I got into the habit of sticking with Golang; and so will this diary. Both his examples ("go…
Well, I write some Go and I agree with OP. As soon as you aren't too sure of where to looks, Google doesn't either and return garbage results.
Re: Golang Diaries I
#9> First, the name. “Go” has too many meanings and is among the world’s lousiest Google search disambiguators. Enough with this old wives tale. Yes, "Go" is too generic. Nevertheless, Google understands it just fine. Case in point: > "After a few painful instances of searching for things like “go array literals” and “go repl” I got into the habit of sticking with Golang; and so will this diary. Both his examples ("go…
Maybe Google is tailoring your results to bring back sites that include the programming language based on a) your past searching habits and b) the emerging trends for those specific search patterns.
Google's results are highly tailored, thus two people can search for the same term and get different results.
Going back to the original point raised, I too have gotten into the habit of searching for "go lang [query]" rather than just "go [query]" due to the same frustrations in the past. What the author describes isn't a unique quirk he's experienced, it's actually a very common complaint.
Re: Golang Diaries I
#10The post is fun, thanks. I like Tim's idea of "taking the journey" with a programmer on discovering new content. It's certainly the best way to introduce the topic to others. All the potential sticking issues have been handled for you!
I was also excited when he said "I filed a bug on June 6th, and it was fixed on the 12th. Gotta love that.". There is no better feeling than sending a pull request and having someone thank you, merge it, and fix the issue within a few hours or days of you sending it.
In this case, however, I think his joy may be premature. Rob Pike replied to the bug saying it was indeed an issue and either the code or documentation should be fixed. Having Rob Pike reply is a good start, considering he's the primary author of Go. Someone else then came along and fixed it in a way the article's author is unhappy with, though[1].