191–198 of 198 posts
Here is my advice. What github looks charming to me is the wonderful service for free plan users. I think this is wise, build a huge audience, and then "out-teach" them to be their potential customer. Success comes after the fame.
I just use bitbucket.org + Mercurial. More than enough for personal projects, or more, given that it's unlimited. The only limit is amount of users. Switching to Hg was a bit of work, but I've actually learned to like it more than Git. Really though, it's the same kind of thing and I just use both. So I ended up at bitbucket for the same reasons OP built a new site. My way was quicker though.
I use github for the network effects, but how does hg compare to git, speed-wise? I switched to git from bzr because bzr felt awesomely slow, although git is a real pain to use, even when you're familiar with it. I understand that bzr and hg are almost identical, command-wise, but hg is about as fast as git, is that correct? What my workflow consists of is diffs/statuses/commits/pushes/pulls in projects with working…
Hg is slower overall, but scales just as well as git. A huge repo will still be just slightly slower in hg than in git.
Earlier quoted context omitted.
I use github for the network effects, but how does hg compare to git, speed-wise? I switched to git from bzr because bzr felt awesomely slow, although git is a real pain to use, even when you're familiar with it. I understand that bzr and hg are almost identical, command-wise, but hg is about as fast as git, is that correct? What my workflow consists of is diffs/statuses/commits/pushes/pulls in projects with working…
I've yet to find any significant speed difference between git and hg. Hg is slower overall, but scales just as well as git. A huge repo will still be just slightly slower in hg than in git.
I think CodePlane is very cool, but it seems to solve a different problem than the one advertised on the blog. To save my repos "for posterity" on Github without incurring a $100/month bill, I simply create a master repo (say old-projects/) with all my unused repos in it. On the other hand CodePlane seems to be a great solution for collaborative work on lots of private repos. This can save big bucks. I love to see pr…
The one-repo-for-old-projects solution works in some cases, but not really for mine. As a contract developer I often have projects that are under active development for a few months and then go into "maintenance mode". In this case I want separate repos for when maintenance needs to happen. Otherwise that one repo is a mess. I believe this is the kind of problem that CodePlane solves. And I agree with you that its gr…
This is a very desirable use case. For those who don't get it, I'd say the following: - it's nice to use git for all the small side projects one creates, but putting all of them on github is crazy expensive if you like keeping your musings private (though not necessarily b/c you're committed to a closed source ideology :) - the cost factor creates an incentive to misuse git (not using submodules where appropriate) ju…
Earlier quoted context omitted.
Getting a Git repo setup with a web accessible interface is not trivial and for the time spent doing it, you could be doing other things like ... you know ... writing code to make you money.
Gitolite/Gitosis/Gitweb and/or ssh access. I could do it in ~5 minutes. I could hack up an MVP of the features that Github has that I care about in maybe a weekend. That said, I do use and love Github, but I use it for the network effects and general slickness. If I need a private repo, I get off my fat ass and deploy it in less time than it takes to enter my billing address.