Re:Why GitHub’s pricing model stinks (for us)
by mqzaidi on Wednesday February 13, 2013 @07:26AM
(#5212695)
This is precisely the reason why we switched from github to unfuddle. Why should my developers start rationing for repos and start putting everything in one large repository, just so that we don't hit the limit with github. For example, we use node.js heavily, and I would like create npm modules that can be shared across repos, and put them in a repo of their own (so npm can install them). Github's pricing forces me not to do this, and discourages code reuse.
[ Parent
| on HN ]
Re:Why GitHub’s pricing model stinks (for us)
by tomfakes on Wednesday February 13, 2013 @01:29PM
(#5214742)
I used to be a big fan of Unfuddle, and I still have an account there, but the reality is that all of the integrations I use (CI is the most recent one) work great with Github and not at all, or are much harder to configure, with Unfuddle.
Github is creating value with their ecosystem, which is great for them, and, since the code is all in Git, not a complete lock-in if you choose to move.
Re:Why GitHub’s pricing model stinks (for us)
by analog on Wednesday February 13, 2013 @07:41AM
(#5212759)
Is there a reason you wouldn't use public github repos for your npm modules?