um pouco da história do github:
sobre o git curto este artigo, que já passei e repassei pra n amigos nerds, mas vai de novo aqui:
Git is the next Unix
When I first heard about git, I was suspicious that there could be anything special about it, but after watching Linus’ talk about it, I was… even more suspicious. I tried it anyway.
When I tried it, I realized something right away: what made git awesome was actually none of the things Linus had talked about, not really. Those things were more like… symptoms of the underlying awesomeness. Yes, git is fast. Yes, it is distributed. Yes, it is definitely not CVS. Those things are all great, but they miss the point.
What actually matters is that git is a totally new way to operate on data. It changes the game. git has been described as “concept-heavy”, because it does so many things so differently from everything else. After some reflection, I realized that this is far truer than I could see at first. git’s concepts are not only unusual, they’re revolutionary.
Note the key advantages Git offered in each step:
1. Git creates a full repository with this command. With Subversion, you’re just checking out the files in the repository.
2. With each branch, no new files are created in the project file hierarchy on your system. Since you have a full local repository, Git creates the files you need on the fly by processing the recorded changes. With Subversion, you have to create every branch remotely on the server. This can get messy depending on the size of your team. If you decide to control branching to keep things clean, you forfeit the power branching offers.
3. With Git, we only push our work to the server AFTER collaboration (more below). With Subversion, it all hits the server.
4. Again, no file system work. Since we’re using a local repository, we let Git handle the details of removing the branch. With Subversion, you still have the old copy until you update. You either have to clean up manually, or “update” to clean up local and remote copies.
There are literally hundreds of features for both Git and Subversion. While you may have detailed reasons to choose one over the other, I think these 3 high level reasons are strongly convincing in favor of Git. If you have differing opinions, I’d love to hear them.