3 ms·
> It is an overkill for a small project with a central repository - what we usually have, leading to a large conceptual overhead. I strongly disagree. All my p
by jkubicek 13y ago
> It is an overkill for a small project with a central repository - what we usually have, leading to a large conceptual overhead.
I strongly disagree. All my projects use git and the majority of them are small with a central repository.
As someone who learned Git and SVN at the same time, I think git has an undeservedly bad reputation. There are many workflows where Git is much easier to grasp conceptually (initializing a new repo, branching, how do I work on an airplane?) I think people who are comfortable with SVN tend to forget that, other than the confusion around staging, it's easier for rank beginners to learn the basics of Git than the basics of SVN.
- stared 13y agoIf for someone Git is too hard then Mercurial is a great choice. Better (safer, more powerful) than SVN and perhaps even - easier. (Just now I am converting some scientific collaborators to use Mercurial for small projects. Still, for code I use Git... but mainly because of GitHub.)