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

151–160 of 244 posts

Re: Go is moving to GitHub

#151

Post by akerl_ »

chrisconroy wrote: post #121
shurcooL wrote: post #49

Earlier quoted context omitted.

They've really made it easier to collaborate. Their website design is beautiful, consistent, making it delightful to use everyday. They fix issues quickly, are reliable, and have top notch customer support. They try to be at the top of their game and offer features to make our work easier (while maintaining simplicity, similar to Go). You can edit posts to fix typos, and GitHub Flavored Markdown is efficient to write…

You must have dealt with a completely different company and product. The public github is a lot better than the enterprise version at least in terms of stability. Still, both lack a lot of basic issue tracker and code review features. Github enterprise was a disaster with just a couple hundred users. Under the load of just a few hundred users it died almost every day. Their support team couldn't figure it out. We had…

Github Enterprise has supported disabling force pushes for at least a year.

Re: Go is moving to GitHub

#152

Post by enneff »

yarou wrote: post #140
enneff wrote: post #60

Earlier quoted context omitted.

We (the Go team) regularly have conversations about all kinds of programming paradigms, because we're into that kind of stuff. Some of us really like functional programming languages. But Go is not that kind of language, so those primitives do not belong there. Go is not everything to everyone, and it would be a mistake to try to make it that way. That doesn't mean that we don't see those things as generally valuable…

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.

You appear to know both Haskell and C, but find Go's syntax hard to deal with? This is one of the weirdest Go complaints I've read, for sure. Syntactically, it's just one of the many Algol/pascal-style imperative languages of the last 40 years. Most people get used to it quickly.

At least it's nice and unambiguous.

Re: Go is moving to GitHub

#153

Post by natefinch »

beagle3 wrote: post #141
Matumio wrote: post #130

Earlier quoted context omitted.

IMO the main problem is that the command vocabulary is a mess. Do I need a soft, mixed or hard reset? Can I use "reset" to revert a single file, or do I need "checkout" for that? After years of using and loving git, this still confuses me. It's all logical in terms of git internals, but I'm not thinking in those terms when I want to revert something.

There are countless git frontends (easygit and git legit) that come to mind, and yet they all see negligible use. I think the cognitive load of using git is overrated. Yes, it could probably be simpler. No, you probably can't make simple and intuitive for everyone while retaining all the features. Given that it's also easy to work with e.g. subversion or mercurial and a git bridge, so you can use the client of your c…

The git CLI is a mess. It's inconsistent even within its own commands. For example, sometimes specifying remote and branch is done as "remote/branch" and sometimes as "remote branch".

It even uses different words for the same thing - sometimes remove, sometimes rm sometimes -d.

Common actions often require obscure command lines, like "make a new branch" which is git checkout -b instead of just "git branch".

The reason people don't use other git frontends is that a vast majority of the help topics already out there only reference git itself. So if you want help for rebase, for example, if you're using some frontend that re-kajiggers the command line, all that help is now useless, or even worse, potentially downright incorrect.

Re: Go is moving to GitHub

#154

Post by NateDad »

dsymonds wrote: post #44
icebraining wrote: post #41

Earlier quoted context omitted.

How many Github projects accept git format-patch submissions? There's functionality beyond the basic DVCS commands.

In Go's case, we will be using Gerrit (elsewhere) for accepting submissions. GitHub will only be used as a source code mirror, wiki and issue tracker.

Wait wait wait... no pull requests? There's no way you could just hook up PR's to gerrit? Using github just as a mirror seems to defeat the entire purpose of github, which is to encourage more community members to contribute.

Re: Go is moving to GitHub

#155

Post by NateDad »

srcmap wrote: post #75
bbx wrote: post #45

Google hosting Go on GitHub. Microsoft hosting .NET on GitHub. It must feel like an accomplishment to be implicitly endorsed by these companies. Considering open source's history, you'd think its primary management tool would be open source as well. I guess it's GitHub's combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.…

Use go for a few month, loving it. but I miss not having exception compare to Python. Is the golang spec still tightly controlled by 3 wisemen in Google and no feature is allowed to add to the language without all three in total agreement? BTW, I like 98% of their language decide choices and absolutely LOVE the compilation speed of the program.

No, it's not controlled by them anymore. Possibly in the early days it was, but now it's much more community controlled.

You'll never get exceptions in Go. No one who has used go for a significant period of time wants exceptions. Error values are far superior (given the other features of the language, like multiple returns and interfaces for the error types).

You should continue to use Go, I don't think you'll miss exceptions after long. I understand the view, though... first time I saw Go I thought "No exceptions? Pass!". But I got over it, and now I've seen the error of my ways :) There's an amazing freedom that comes with knowing that random functions you call can't exit your function without your control.

Re: Go is moving to GitHub

#156

Post by NateDad »

yarou wrote: post #140
enneff wrote: post #60

Earlier quoted context omitted.

We (the Go team) regularly have conversations about all kinds of programming paradigms, because we're into that kind of stuff. Some of us really like functional programming languages. But Go is not that kind of language, so those primitives do not belong there. Go is not everything to everyone, and it would be a mistake to try to make it that way. That doesn't mean that we don't see those things as generally valuable…

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.

What?! If anything, your use of C should make Go's syntax really familiar (aside from putting the name before the type, which doesn't take long to get used to). It's exactly like any other C-like imperative language. C, C++, Java, C#, even Javascript. Those are pretty traditional langauges. Haskell is not what I think most people would call a "traditional language".

What exactly is your problem with the syntax?

Re: Go is moving to GitHub

#157

Post by Shizka »

tsmarsh wrote: post #150

I guess its official, misogyny is ok in our industry. Have we forgotten about: http://lmgtfy.com/?q=github+misogyny ? I'm not sure github even experienced a dip in traffic. There are github alternatives, it took me 30 minutes to remove my github subscription and migrate my repos to bitbucket.

I will bite.

How does using Github even remotely contribute to accepting misogyny in our industry?

Re: Go is moving to GitHub

#158

Post by NateDad »

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 have to agree that not using pull requests is missing out on the best feature of github. It's the social, low-overhead way to contribute to a repo.

It seems like it must be possible to hook up a bot to github that watches for pull requests and submits them to gerrit... the Juju team has a bot that does that for our Reviewboard integration. It won't work for more complicated workflows that github doesn't support, like dependent branches or whatever, but it lowers the barrier of entry for initial contributors that just want to submit a simple fix. And the more advanced users can just submit directly to our Reviewboard instance if they want the more advanced features.

Also, the public fork on Github is actually a feature - it means others can easily see what you're working on. You need off-site storage for your personal work anyway, right? You're not going to keep it local on your laptop, so you'll need a branch somewhere regardless.

Re: Go is moving to GitHub

#159

Post by Arnt »

Shizka wrote: post #157
tsmarsh wrote: post #150

I guess its official, misogyny is ok in our industry. Have we forgotten about: http://lmgtfy.com/?q=github+misogyny ? I'm not sure github even experienced a dip in traffic. There are github alternatives, it took me 30 minutes to remove my github subscription and migrate my repos to bitbucket.

I will bite. How does using Github even remotely contribute to accepting misogyny in our industry?

There was an ugly affair there.

Github's handling of the affair is difficult to judge from outside. At least it seems that management's handling of this affair did not increase future misogyny at the company.

Re: Go is moving to GitHub

#160

Post by lxj »

tsmarsh wrote: post #150

I guess its official, misogyny is ok in our industry. Have we forgotten about: http://lmgtfy.com/?q=github+misogyny ? I'm not sure github even experienced a dip in traffic. There are github alternatives, it took me 30 minutes to remove my github subscription and migrate my repos to bitbucket.

Have you assessed Atlassian's culture and concluded its constituents promote gender equality?

http://www.dailymail.co.uk/news/article-2649354/Australian-t...

Does boycotting Github for the rest of time over a scandal achieve anything?

Nonetheless, your post has value in that I'm now thinking about gender equality in technology. Thank you.

Post reply on HN