Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Golang Diaries I

tbray.org

Post reply on HN
Print view View original

21–30 of 79 posts

Re: Golang Diaries I

#21

Post by zurn »

Smerity wrote: post #10

The 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 t…

> Having Rob Pike reply is a good start, considering he's the primary author of Go

According to himself and the Go FAQ he's just one member in the team, the beginnings are described as "Robert Griesemer, Rob Pike and Ken Thompson started sketching the goals for a new language on the white board on September 21, 2007"

Re: Golang Diaries I

#22

Post by NateDad »

Please call it Go, not golang. Golang is the domain name of the language's website, a useful hashtag, and an occasionally useful search term. It is not the name of the language should not be used as such. The language is Go, it should be called Go.

Re: Golang Diaries I

#23

Post by corresation »

karka91 wrote: post #6

Golang 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.

The language was conceived under four years ago, and only quite recently was considered production ready.

Yes, in the pantheon of programming languages it is very new. Further many of us have stayed at a distance until the ecosystem of supporting libraries and supports are robust enough (I love everything about developing, but my primary concern remains paying the bills and pulling in the lucre, so exploratory or academic languages don't get prioritized).

I am quite sure that a large percentage of HNers are interested in the language, but haven't yet taken the dip and thus are intrigued by things like this.

Re: Golang Diaries I

#24

Post by corresation »

unwind wrote: post #14
Smerity wrote: post #10

The 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 t…

Yeah, the final comment on the bug is also from Mr Bray, and isn't exactly a "thanks". I was quite surprised by that combination after reading the diary blog post, they don't really match up.

Agreed, that bug is quite a bit different from the impression in the blog post. Tim is completely right, however: Why can't he use the automatically differentiated leading underscore test? And the fix of the documentation is, as he mentioned, just as wrong as it already was. Now I wonder if his bug comment was sarcastic, because it would be had I written it.

Re: Golang Diaries I

#25

Post by espadrine »

unwind wrote: post #14
Smerity wrote: post #10

The 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 t…

Yeah, the final comment on the bug is also from Mr Bray, and isn't exactly a "thanks". I was quite surprised by that combination after reading the diary blog post, they don't really match up.

That's because Tim Bray posted the blog post, after which he read the patch (the comment was submitted today).

Re: Golang Diaries I

#26

Post by saljam »

jzelinskie wrote: post #12

>Golang will not let you compile if there’s an import or declared variable that’s unused. OK, I understand that Cleanliness Is Next To Godliness, but this is seriously slowing me down; probably a third of my attempts to run my damn program fail because I’ve forgotten to remove debugging apparatus, or I’ve sketched in a variable but not used it yet. How about a compiler switch or something? I don't find this an issue…

Furthermore, Java is quite happy to let you do COLS[1] = "Green". All that is constant about that array is the reference.

Re: Golang Diaries I

#27

Post by Symmetry »

I’m also unconvinced that the distinction between := and = is essential; feels like unnecessary ceremony.

I think that's actually almost my favorite thing about the language, I don't know how many times I've wished that Python and Lua worked that way. Having a low-ceremony means of declaration while also preventing you from accidentally over-assigning something when you want to be declaring it is really nice.

Re: Golang Diaries I

#28

Post by rgbrgb »

NateDad wrote: post #22

Please call it Go, not golang. Golang is the domain name of the language's website, a useful hashtag, and an occasionally useful search term. It is not the name of the language should not be used as such. The language is Go, it should be called Go.

He explains in the article that he does this as a search differentiator.

Re: Golang Diaries I

#29

Post by justinhj »

jzelinskie wrote: post #12

>Golang will not let you compile if there’s an import or declared variable that’s unused. OK, I understand that Cleanliness Is Next To Godliness, but this is seriously slowing me down; probably a third of my attempts to run my damn program fail because I’ve forgotten to remove debugging apparatus, or I’ve sketched in a variable but not used it yet. How about a compiler switch or something? I don't find this an issue…

Using go mode, autocomplete and goflymake helps a lot on emacs too.

Re: Golang Diaries I

#30

Post by BarkMore »

corresation wrote: post #24
unwind wrote: post #14

Earlier quoted context omitted.

Yeah, the final comment on the bug is also from Mr Bray, and isn't exactly a "thanks". I was quite surprised by that combination after reading the diary blog post, they don't really match up.

Agreed, that bug is quite a bit different from the impression in the blog post. Tim is completely right, however: Why can't he use the automatically differentiated leading underscore test? And the fix of the documentation is, as he mentioned, just as wrong as it already was. Now I wonder if his bug comment was sarcastic, because it would be had I written it.

Why can't he use the automatically differentiated leading underscore test?

The go tool currently ignores all files with a leading '_' in the name. Changing the tool to use a file with the name '_test.go' complicates the rule for ignored files and might break an existing project. The workaround of using 'all_test.go' is not onerous.

Post reply on HN