6 ms·

As far as I'm concerned, one of the best features of git is how easy it is to create new repos. Setting up a new repo for a new weekend side project, or splitti

As far as I'm concerned, one of the best features of git is how easy it is to create new repos. Setting up a new repo for a new weekend side project, or splitting out a large codebase that's gotten unwieldy into a few separate repos, should be a no-brainer. BitBucket lets me have as many private repos as I want, since they make their money when you want to add collaborators; GitHub's payment structure forces me to consciously think about how many repositories I have. I prefer GitHub to BitBucket in terms of their web UI/UX, but I really don't like that psychological shift.

ianstormtaylor 13y ago
Honestly this has never been a problem for me. How many private repos do you really need? It can't cost that much per month. The things most people are working on just aren't that important. Or better yet, they _benefit_ from being public.
- dangrossman 13y ago
  I'm like the guy you replied to. I make a lot of repos in the course of work, play, and learning. Most of them I'd like to keep around, including history. I could fit everything on one CD; storage is cheap. Github would want $100/month to host those repositories. BB wants nothing, or http://repositoryhosting.com http://repositoryhosting.com will host them all with backups for $6. I don't have to think about costs when typing "git init", and I don't have to think about scrubbing passwords/keys/personal information when typing "git push"; repo-count pricing and public by default have high psychological overhead. GH's pricing doesn't work for me, so I don't keep my private repos there. Not a big deal, but I also don't think it indicates there's something wrong with how I work, the value of my code, or how I spend my money.
- eropple 13y ago
  I have 38 private repos on Bitbucket. None benefit me by being public.
- drivebyacct2 13y ago
  Seriously? I have 20 different Git repos for various things that either can't or simply don't make sense to be public. Sure, GitHub's great and I have a paid account with them (not even the minimum), but I certainly have to rely on BitBucket as well.
yeukhon 13y ago
You understand to create a repo you issue one command, regardless of whether you use git or hg? Also, GitHub doesn't support Hg is a major drawback for a lot of people. Git has a relatively higher learning curve, although certain commands in Git are really really awesome I have to admit.
- lazerwalker 13y ago
  Replace 'git' with 'DVCS'. My choice of git over hg isn't particularly relevant to the larger point I was making.

ianstormtaylor 13y ago

Honestly this has never been a problem for me. How many private repos do you really need? It can't cost that much per month. The things most people are working on just aren't that important. Or better yet, they _benefit_ from being public.

dangrossman 13y ago
I'm like the guy you replied to. I make a lot of repos in the course of work, play, and learning. Most of them I'd like to keep around, including history. I could fit everything on one CD; storage is cheap. Github would want $100/month to host those repositories. BB wants nothing, or http://repositoryhosting.com http://repositoryhosting.com will host them all with backups for $6. I don't have to think about costs when typing "git init", and I don't have to think about scrubbing passwords/keys/personal information when typing "git push"; repo-count pricing and public by default have high psychological overhead. GH's pricing doesn't work for me, so I don't keep my private repos there. Not a big deal, but I also don't think it indicates there's something wrong with how I work, the value of my code, or how I spend my money.
eropple 13y ago
I have 38 private repos on Bitbucket. None benefit me by being public.
drivebyacct2 13y ago
Seriously? I have 20 different Git repos for various things that either can't or simply don't make sense to be public. Sure, GitHub's great and I have a paid account with them (not even the minimum), but I certainly have to rely on BitBucket as well.

yeukhon 13y ago

You understand to create a repo you issue one command, regardless of whether you use git or hg? Also, GitHub doesn't support Hg is a major drawback for a lot of people. Git has a relatively higher learning curve, although certain commands in Git are really really awesome I have to admit.

lazerwalker 13y ago
Replace 'git' with 'DVCS'. My choice of git over hg isn't particularly relevant to the larger point I was making.