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

31–40 of 244 posts

Re: Go is moving to GitHub

#31

Post by shadowmint »

patrickaljord wrote: post #18
yohanatan wrote: post #13

Which will have no bearing on the case of Go. Go has already been relegated to the bottom of the quality bin for my purposes by its designer(s)' ignorance of the last 30 years of type system research and hostility towards the functional style. See: https://groups.google.com/forum/#!topic/golang-nuts/RKymTuSC...

Really? You've managed to mention the lack of generics on a thread announcing moving go to github? Is this a parody comment or are you serious?

Why does hacker news not have a reddit style 'below threshold' to display none subthreads? :/

Re: Go is moving to GitHub

#32

Post by enneff »

melvinmt wrote: post #28
virtue3 wrote: post #6

Earlier quoted context omitted.

thank you. Missed that in the article (was skimming >_> )

Me too, my brain is wired to read Gerrit as a common Dutch first name, so I thought he was talking about a person named Gerrit.

It is! Gerrit (our new code review system) is named after Gerrit Rietveld (the designer), as it Rietveld (our old code review system).

Re: Go is moving to GitHub

#33

Post by hahainternet »

yohanatan wrote: post #20
patrickaljord wrote: post #18

Earlier quoted context omitted.

Really? You've managed to mention the lack of generics on a thread announcing moving go to github? Is this a parody comment or are you serious?

Totally serious. And, it's not just the lack of generics-- that's just the tip of the iceberg.

What problems have the lack of generics caused you in development?

Re: Go is moving to GitHub

#34

Post by andrewchambers »

negated wrote: post #10
jeffreyrogers wrote: post #5

It is great to see so many projects moving to git and GitHub in particular. GitHub is incredibly helpful for quickly taking a look at a project and figuring out what areas of a project are still evolving and being actively developed.

You could also say that everyone moving to GitHub is leading to a dangerous centralized monoculture that evaluates software quality based on how well it fits GitHub's conventions.

git is still git - people don't even need a github account to have full functionality.

Re: Go is moving to GitHub

#35

Post by dang »

shadowmint wrote: post #31
patrickaljord wrote: post #18

Earlier quoted context omitted.

Really? You've managed to mention the lack of generics on a thread announcing moving go to github? Is this a parody comment or are you serious?

Why does hacker news not have a reddit style 'below threshold' to display none subthreads? :/

I feel your pain. This is coming. In the meantime, we've detached this subthread from its parent so we can mark it off-topic.

All: predictable flamewars add no new information, therefore have a signal/noise ratio of zero, and therefore are off topic for Hacker News.

Re: Go is moving to GitHub

#37

Post by reledi »

thejosh wrote: post #27
jeffreyrogers wrote: post #5

It is great to see so many projects moving to git and GitHub in particular. GitHub is incredibly helpful for quickly taking a look at a project and figuring out what areas of a project are still evolving and being actively developed.

Moving to git is great, moving to github can be terrible for some projects that are more collaborative, as if you want to change someones PR you cannot..

You can makes changes to a PR that you didn't open.

If you want to change the title, edit/delete comments, close the PR, assign a person or labels then you'll need the proper permissions.

If you want to make changes to the code you'll need to have push access to the same repo (which is usually the case if you're on the same team because then you don't need to use forks). Otherwise you can always amend the commit(s) before merging them into master.

Re: Go is moving to GitHub

#38

Post by zwily »

thejosh wrote: post #27
jeffreyrogers wrote: post #5

It is great to see so many projects moving to git and GitHub in particular. GitHub is incredibly helpful for quickly taking a look at a project and figuring out what areas of a project are still evolving and being actively developed.

Moving to git is great, moving to github can be terrible for some projects that are more collaborative, as if you want to change someones PR you cannot..

They're using Gerrit for code review, where you can modify patches submitted by other people.

Re: Go is moving to GitHub

#39

Post by dang »

enneff wrote: post #30
yohanatan wrote: post #29

Earlier quoted context omitted.

To the siblings to this post: it seems rather unlikely as the research is being generated at a rate that far exceeds any one person's ability to read it (especially when they are already busy marrying C and CSP [which is easy to build as a library or add-on to any other existing language] & type theory isn't their specialty).

So, you're criticising someone for not doing something that's impossible? Just stop.

It was at least interesting how quickly those goalposts moved.

Re: Go is moving to GitHub

#40

Post by reledi »

enneff wrote: post #19
tkrajcar wrote: post #11

Earlier quoted context omitted.

I'm curious what Gerrit gets them that Github doesn't have natively, too.

There are a lot of things lacking about GitHub's code review process (pull requests). Off the top of my head: - Merging a pull request (almost) always creates a merge commit, polluting the change history. Gerrit will automatically rebase the changes atop the master branch head, leaving a nice linear history. - Pull requests require the contributor to create a public fork of the repository they're committing to. I can…

> Pull requests require the contributor to create a public fork of the repository they're committing to.

You can create Pull Requests within a repository. You don't need to fork the repository if you have push access.

Post reply on HN