Git on Google Code vs GitHub

Google Code now supports Git as a repository option.  Here are my first impressions of pushing a git repository to Google Code compared to GitHub:

Cons

• Project name has to be globally unique and all lowercase.
  On GitHub my projects are under my user directory.  So, I don't have to compete for a unique project name.  And I can used mixed-case, which is normal for most languages.
• No automatic readme.  GitHub has a convention where a readme file is automatically shown on your project home page.  And it is prettified if it uses markdown syntax.
• No instructions for pushing your existing repo.
  
  After you create your project you are not presented with instructions for pushing your code via git.  In fact, you aren't presented with many instructions at all.  If you navigate to the source page you will see instructions for cloning your new repo, but no instructions for a pre-existing repo..
  
  As a side note, you can push an existing repo to your Google Code project.  Follow similar steps as you would on GitHub:
• Go to the source tab to find your source URL and a link to a generated password
• cd <existing git repo>
• git remote add origin <url>
• Paste your password when prompted
• git push -u origin master

Pros

• Pick your license.  There doesn't seem to be a conventional way to specify your open source license on GitHub.
• Even though Google Code doesn't have a convention for using your readme file, you can use wiki syntax to update your project description.  It does not track changes.
• There is better integration between the project wiki and the project home page.
• Integration with other Google services like Analytics and +1
• You can pick a project logo...

For the time being, I'll be sticking with GitHub.  But, I'm glad to see some competition.