News for hackers. Stuff that matters.
Re:Facebook Go Libraries by nahname on Thursday November 13, 2014 @09:13AM (#8601551)
Looks more like Naitik Shah's open-source libraries.
Re:Facebook Go Libraries by csmajorfive on Thursday November 13, 2014 @10:09AM (#8601850)
These were all developed on the Parse team. Naitik is a huge contributor :)

I believe we're the only ones doing using Go in production at Facebook. Join us! https://parse.com/about#jobs

Re:Facebook Go Libraries by harisamin on Thursday November 13, 2014 @11:24AM (#8602339)
Nice. Thanks for open sourcing these libs :)
Re:Facebook Go Libraries by jzelinskie on Thursday November 13, 2014 @01:24PM (#8603076)
I've heard there are a few other little sprinkles of Go in other places, but no large codebases like this.
Re:Facebook Go Libraries by akavel on Thursday November 13, 2014 @09:34AM (#8601664)
He seems the main committer there, indeed... but "Naitik Shah's open-source libraries" seem to be present already at: https://github.com/daaku?tab=repositories ... so what is the "facebookgo" thing then?

edit: the files have "Copyright Facebook, Inc." anyway

Re:Facebook Go Libraries by Shish2k on Thursday November 13, 2014 @10:03AM (#8601818)
I wonder why these aren't under the main facebook account ( https://github.com/facebook ) o_O?
Re:Facebook Go Libraries by twotwotwo on Thursday November 13, 2014 @03:01PM (#8603696)
It gives them more freedom in package names. It's nice when a package name is the same as the last element of the URL, and that URL's reasonably short. And you repeat the package name whenever you use an identifier from the package, so it's good if it's 1) short, and 2) if possible makes the full identifier read nicely à la counting.Reader.

With their own GitHub username, they can just use whatever word they want for the package name (tool, counting, stack, subset, grace, inject) without risking a collision with other Facebook projects.

Re:Facebook Go Libraries by couchand on Thursday November 13, 2014 @11:57AM (#8602543)
Better organization? Once you start to have more than a few pages of projects on a single group it starts to get very difficult to find them on GitHub unless you know exactly what you're looking for.