Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
The main differences between git and svn are distribution and good branching support in development (branches).
SVN supports branches, of course, but when branches are complex (branches are merged), there are unexpected conflicts and so on. Although, if you have a classic scheme - a feature branch from the master (trunk) and a reverse merge to the master (trunk) - the difference is almost imperceptible.
About distribution: SVN has a central server, git has a graph of servers, although 99% of developers use a local repo + one remote, i.e. in fact - the same central server. But, since the turnip is local, git is very fast in switching branches.
There are still a lot of differences and both pros and cons for each software. Although today SVN is becoming less and less common, but in general for many workgroups it is quite enough for a full-fledged work. On the other hand, knowing git is also a must today, because it's almost a standard;)
If you look like this at first glance for "why svn is better"...
But I wouldn't say that svn is fine and git is not. He's just different and with his cockroaches. I myself worked on SVN for a long time, then slowly moved to git, mainly because of the pitfalls of complex branching.
Lower entry threshold. Even a person with no IT skills, at the level of an average accountant, can learn to work with SVN.
For professional IT people git.
svn - centralized storage
Such a case is very rare
svn should be used if one person will work with the project
The only plus is the linear numbering of commits. It turns out a human-like chronology.
SVN is better than Git in that it doesn't try to turn your Windu into Unix and doesn't drag along a bunch of garbage ... er, dependencies that stem from the unwillingness of Git developers to agree and write everything in one language ... or not one, but compiled, in order to then assemble the object code into executable modules.
So SVN is 5 meters of EXE/DLL of SVN itself, and Git is 200 (400?) meters, including MSYS, Cygwin and Perl in addition to Git itself. For whom the size is not an argument - there is the concept of the complexity of ownership: in a large and complex system there are more points where something can break.
Nobody argues about generations and distribution. It just so happened that by the time distributed VCS appeared, non-system programmers stopped writing in compiled languages ... In terms of uniformity, Mercurial is better, but Python is slow, infection!
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question