Are there really any reasons to use Google Code when GitHub is kicking so much ass?
Its a distributed system. Use them both if you want. Each have their strengths.
Code.Google.com now supports git
11–20 of 83 posts
Re: Code.Google.com now supports git
#12Waiting to get invited to a Google Code drinkup.
Re: Code.Google.com now supports git
#13That's great, but I'm still slowly moving my projects over to Github.
1. I get much more engagement from random developers on Github. On Github, random people will fork and add features, do code reviews and leave comments. All of these things are technically possible on Google Code but nobody does it—probably due to the usability but possibly also a cultural problem. Github has a strong culture of collaboration because they strongly emphasize it in the user's experience.
2. Managing forks and pull requests is easier on Github. I want my life as a maintainer to be as easy as possible.
3. Notifications: For a long time, Google Code notifications simply didn't work for me, at all. I'd randomly stumble on one of my older projects and noticed 5 new issues opened that I didn't know about, I felt like I betrayed my users for 6+ months. Now they seem like they do, but some trust has been lost.
4. Multiple choices of documentation markup on Github is appealing.
5. The code browsing feature on Google Code feels like its own application. When you open a Github project, first thing you see is the code. On Google Code it takes 2 more clicks (that's 1 more click than Bitbucket). Think about what's the most important thing here—the code, and Github got it right.
As far as version control goes, I'm happy with either Git or Mercurial.
Re: Code.Google.com now supports git
#14I see it also still supports horrible UI. Pass.
Unhelpfully snarky way to put that. Why not say "Getting Git is great. I hope that the UI is improved soon too."?
Or even better, explain what about the UI could be improved. I've been using Google Code for several years, and I love the UI.
Re: Code.Google.com now supports git
#15While we're on the subject of git, can anyone recommend me a Git host that doesn't limit the number of private repositorys? $8 a month and only five private repositories is really restricting, and my only real complaint with GitHub.
Re: Code.Google.com now supports git
#16I see it also still supports horrible UI. Pass.
Google Code and Git are actually perfect for each other -- both have horrible UIs.
Re: Code.Google.com now supports git
#17That's great, but I'm still slowly moving my projects over to Github. 1. I get much more engagement from random developers on Github. On Github, random people will fork and add features, do code reviews and leave comments. All of these things are technically possible on Google Code but nobody does it—probably due to the usability but possibly also a cultural problem. Github has a strong culture of collaboration becau…
(Speaking purely for myself here.) I agree the code is important, but I think a cohesive project is more important. Github presents itself as a giant pastebin for code, with "projects" bolted on. Google Code presents projects first, and puts the code at an even level with every other part: bugtracker, downloads, wiki.
(That said, I agree pull requests would be cool.)
Re: Code.Google.com now supports git
#18That's great, but I'm still slowly moving my projects over to Github. 1. I get much more engagement from random developers on Github. On Github, random people will fork and add features, do code reviews and leave comments. All of these things are technically possible on Google Code but nobody does it—probably due to the usability but possibly also a cultural problem. Github has a strong culture of collaboration becau…
(Speaking purely for myself here.) I agree the code is important, but I think a cohesive project is more important. Github presents itself as a giant pastebin for code, with "projects" bolted on. Google Code presents projects first, and puts the code at an even level with every other part: bugtracker, downloads, wiki. (That said, I agree pull requests would be cool.)
While I agree with you on the facts of projects vs code, I actually LOVE that the PROJECT isn't
on github. It makes the wily nilly use/patches from 3rd parties so much easier. It makes Google Code feel a little too sourceforgey.
Re: Code.Google.com now supports git
#19Earlier quoted context omitted.
Unhelpfully snarky way to put that. Why not say "Getting Git is great. I hope that the UI is improved soon too."?
Or even better, explain what about the UI could be improved. I've been using Google Code for several years, and I love the UI.
For starters:
What is the #1 reason to visit a project page? To download the source. Does the #2 reason come even close? No. So why in the world is the repo URL not on the front page, and easy for me to copy/paste into a terminal? Why? Github even has a button that will copy it to the clipboard for you!
Re: Code.Google.com now supports git
#20Are there really any reasons to use Google Code when GitHub is kicking so much ass?
Its a distributed system. Use them both if you want. Each have their strengths.
Its a distributed system. Use them both if you want. Each have their strengths.
This is what I do. I like the way Google Code is oriented around giving you more of a "project" view, so I have a Google Code page for my projects, but I replaced the "Source" link with the link to the corresponding Github repo. I treat the Github repo as the primary repo for development, but I do use git-svn to push the code to Google Code SVN as well.. I figure it makes a convenient "read only" mirror for anybody who just wants to check the code out, play with it, whatever, but who isn't really interested in contributing... or for people who don't know how to use Git yet.