Live data from Hacker News

Go is moving to GitHub

groups.google.com

101–110 of 244 posts

Re: Go is moving to GitHub

#101
Now all we need is Jeff Bezos to buy Github :-) That would be funny.

But on the story this is a great move, Github is much nicer than Google Code and more actively supported. I had not heard of Gerrit before and that was a really pleasant discovery. Now to figure out how to get that setup at the office.

Re: Go is moving to GitHub

#102
post #90
post #58

Earlier quoted context omitted.

Rob didn't really say anything about map, filter, and reduce in that thread. His comments should be taken as being in addition to the earlier comments by Ian Lance Taylor, another member of the Go team. You should address the gaps in your own knowledge before criticising others. For instance, you're obviously unaware that Rob designed and implemented a whole language based around map/reduce/filter style operations: h…

I think his obvious implication is that Go doesn't need map, filter and reduce because (if I may summarize) "line feed is just a single character". That's just really poor (and silly) reasoning honestly. A 12-yr old could look deeper. For instance: -. Is 'writing' code all that matters? -. Aren't there in fact 10s or 100s or 1000s more readers to code than writers (including the original author also as a reader)? -.…

Why the downvotes? Bigots?

Re: Go is moving to GitHub

#103
post #90

Earlier quoted context omitted.

I think his obvious implication is that Go doesn't need map, filter and reduce because (if I may summarize) "line feed is just a single character". That's just really poor (and silly) reasoning honestly. A 12-yr old could look deeper. For instance: -. Is 'writing' code all that matters? -. Aren't there in fact 10s or 100s or 1000s more readers to code than writers (including the original author also as a reader)? -.…

Why the downvotes? Bigots?

Rob, myself, and others have written tomes on this, on Hacker News, golang-nuts, and elsewhere. If you're trying to have an argument with Rob (he's not reading this, btw) over some pithy statement he made in February, you're wasting your time.

Re: Go is moving to GitHub

#104
post #90

Earlier quoted context omitted.

I think his obvious implication is that Go doesn't need map, filter and reduce because (if I may summarize) "line feed is just a single character". That's just really poor (and silly) reasoning honestly. A 12-yr old could look deeper. For instance: -. Is 'writing' code all that matters? -. Aren't there in fact 10s or 100s or 1000s more readers to code than writers (including the original author also as a reader)? -.…

Why the downvotes? Bigots?

You've written tomes on how wasting vertical space and multiplying syntactic noise is a good idea? Even if so: ideas are not measured by the volume of noise you write in support of them.

Re: Go is moving to GitHub

#105

Earlier quoted context omitted.

Why the downvotes? Bigots?

You've written tomes on how wasting vertical space and multiplying syntactic noise is a good idea? Even if so: ideas are not measured by the volume of noise you write in support of them.

At the risk of prolonging this insufferable "conversation": my point is that it has been discussed to death, and you're being down voted because nobody is interested in discussing it with you, or even hearing you discuss it.

Re: Go is moving to GitHub

#106

Earlier quoted context omitted.

Why the downvotes? Bigots?

You've written tomes on how wasting vertical space and multiplying syntactic noise is a good idea? Even if so: ideas are not measured by the volume of noise you write in support of them.

[deleted]

Re: Go is moving to GitHub

#107
post #80

Earlier quoted context omitted.

Admitting Code is going nowhere, and seemingly for the first time in living memory, playing geek marketing catch-up with Microsoft :) I really love the new MS.

As someone has already mentioned Google already has stuff on Github. Dart: https://github.com/dart-lang And lots of other stuff: https://github.com/google

Yeah - AFAICT, Go is only taking this long because custom import path checking [1] needs to land in Go 1.4 first to make sure that users get rid of their pointers to code.google.com.

[1] https://docs.google.com/document/d/1jVFkZTcYbNLaTxXD9OcGfn7v...

Re: Go is moving to GitHub

#108
post #103

Earlier quoted context omitted.

Why the downvotes? Bigots?

Rob, myself, and others have written tomes on this, on Hacker News, golang-nuts, and elsewhere. If you're trying to have an argument with Rob (he's not reading this, btw) over some pithy statement he made in February, you're wasting your time.

You've written tomes on how wasting vertical space and multiplying syntactic noise is a good idea? Even if so: ideas are not measured by the volume of noise you write in support of them.

Re: Go is moving to GitHub

#109
post #71

Earlier quoted context omitted.

Now we just need Apple's Objective C / Swift to move to github. :) Sorry, not going to happen. :(

Don't they have a mirror of the compiler on github? https://github.com/llvm-mirror/clang Swift hasn't been included but objective c is there.

Naked Objective-C is not much interesting or useful without accompanying frameworks (Foundation, Cocoa, AppKit etc). Just like publishing only C# compiler without all of .Net framework would be.

Re: Go is moving to GitHub

#110
post #2

Does anyone know what code review system they are using with github?

Hm, I agree that github CR is not good. Glaf they're using Issues though as Github discussions are a _really nice_ way to build software. I personally find Gerrit painful to use, but has critical features, as enneff described. Hope Github really steps up to the plate.

Also, everyone who uses github whould really check out *Sourcegraph's code review stuff. They show you really useful things like:

- exactly what definitions were added/removed/changed (https://sourcegraph.com/github.com/fsouza/go-dockerclient/.p...)

- a diff with jump-to-definition links (https://sourcegraph.com/github.com/fsouza/go-dockerclient/.p...)

- a list of people and projects impacted by the change (https://sourcegraph.com/github.com/fsouza/go-dockerclient/.p...)

Totally gets rid of the "understanding the PR diff" problem others mentioned

Post reply on HN