Subversion considers its future
Posted May 1, 2008 15:40 UTC (Thu) by mikov
In reply to: Subversion considers its future
Parent article: Subversion considers its future
(Quick check - how many svn sub-commands are there: 30. How
many git sub-commands are there: 124.)
I have seen this assertion many times, but in my opinion it is a very misleading exaggeration. The svn subcommands have a practically 1-to-1 correspondence to git. Git has many commands, but:
- All of them don't need to be used
- Git can do a lot more things.
- As somebody else pointed out, many of them are internal.
- Many of them do similar tasks.
I was a heavy and enthusiastic SVN user and it took me about a couple of hours (well, perhaps a day) to learn to use Git as a 100% SVN replacement. Everything beyond that was just a bonus.
I 100% agree that the corporate world is "not ready" for Git. Here is an absurd example of my own experience. Our company's product was being certified for VISA CISP compliance (a set of requirements for secure credit card software).
One of the requirements is that all source code changes must be logged with their author, and there must be a way to verify that the source hasn't been tampered with. We use GIT and all these things (and more) are just a natural part of Git. I thought we would sail through this part.
Alas, when the "examiners" found out that we weren't using a "real" VCS, they probably thought we weren't a "serious" company. It took me hours to explain that to prevent tampering of the source it is sufficient just to record the SHA1 of the commit. I don't think they were happy, because they wanted to see encrypted source CDs hidden in a secure safe.
So, yeah, most of the corporate world is not ready for Git and probably never will. Even SVN will actually be a big improvement for them. They are too incompetent, lazy or unmotivated at various levels of the organization. But that is actually a very good thing for small young companies trying to compete :-)
to post comments)