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

Go is moving to GitHub

groups.google.com

Post reply on HN
Print view View original

241–244 of 244 posts

Re: Go is moving to GitHub

#241

Post by kxo »

gorhill wrote: post #234
yarou wrote: post #140

Earlier quoted context omitted.

A bit OT, but probably the biggest roadblock for me switching over to Go is the wonky syntax. Are there any plans to make Go more accessible to someone coming from more traditional languages? (i.e. like "do" notation in Haskell) I've done the Go tutorial about 5 times last I checked (seriously), and I just can't stomach the syntax. I may be tainted by my years of C, though.

> I just can't stomach the syntax. I may be tainted by my years of C, though. I can't relate to this. That's exactly my years of C that makes Go quite attractive to me. The way I see Go is that it allows me to code as close to metal as C, but without the pains of C -- headers, make file/dependencies, memory management, and more.

> code as close to metal as C

> without ... memory management

Re: Go is moving to GitHub

#243

Post by gorhill »

kxo wrote: post #241
gorhill wrote: post #234

Earlier quoted context omitted.

> I just can't stomach the syntax. I may be tainted by my years of C, though. I can't relate to this. That's exactly my years of C that makes Go quite attractive to me. The way I see Go is that it allows me to code as close to metal as C, but without the pains of C -- headers, make file/dependencies, memory management, and more.

> code as close to metal as C > without ... memory management

Read again. As said "as close to ... but without", I didn't say "close to". If you are unable to make sense of what I wrote, don't blame me for your shortcomings.

Re: Go is moving to GitHub

#244

Post by ojacques »

enneff wrote: post #131
rurounijones wrote: post #126

Earlier quoted context omitted.

Not to be flippant, but if you are not going to use pull-requests, what is the benefit of moving to Github? Will you use the issue tracking system? If not then it just seems like switching to git using the present google code host would suffice from a technical viewpoint.

We will use the GitHub issue tracker, which will allow easy cross references between go issues and other projects on github.

I think this is a great move. Also, very similar to the setup used for the OpenStack (http://openstack.org/) project. All reviews done in Gerrit, published to Github when merged. OpenStack also has the bot which closes GitHub pull requests and redirecting to Gerrit. More on their Gerrit/Github integration here: http://ci.openstack.org/gerrit.html For those interested in doing the same for their own, private projects, there is http://forj.io (full disclaimer, I work on this project). Finally, Gerrit now has an async / TTY based client which works offline (reviews on the go!) with Gertty - https://github.com/stackforge/gertty
Post reply on HN