3 ms·
Wow, the first answer is so... clueless! Git seems to be the "new, shiny, cool" thing. ... As said above: Git adds complexity. Two modes of creating reposito
by chris_wot 13y ago
Wow, the first answer is so... clueless!
Git seems to be the "new, shiny, cool" thing.
...
As said above: Git adds complexity. Two modes of creating repositories, checkout vs. clone, commit vs. push... You have to know which commands work locally and which work with "the server" (I'm assuming most people still like a central "master-repository").
...
Git has the advantage that it's MUCH better suited if some developers are not always connected to the master repository. Also, it's much faster than SVN. And from what I hear, branching and merging support is a lot better (which is to be expected, as these are the core reasons it was written).
Perhaps that is a little harsh. I think the poster just doesn't understand DVCS's.
- m_mueller 13y agoCould you explain what's wrong with that answer? I found it to be spot on, but then again maybe I'm 'clueless' as well.
- chris_wot 13y agoThe whole point of a DVCS is to be decentralized. Linus Torvalds often just posts his own repository and others pull from it. You can use it as a centralized repo, and it works quite well. In fact, it's how I'm doing development with LibreOffice via gerrit. However, even there I find it easier. I find my workflow is to work on a branch, make sure I have clean commits (I use rebase pretty frequently) and branch and merge often. Frankly, it's easier to work with. I find the staging model to be really excellent, and find it just easier to move up and down commits. But looking at the quotes: Git seems to be the "new, shiny, cool" thing. No, no it's not. Two modes of creating repositories Well, sure. It's literally just a shortcut for setting up groups and then changing a global setting. Repos can go from bare to shared reasonably easily. I fail to see the point. checkout vs. clone Checkout checks out a branch of path to the working directory. Clone gets an entire repository and "clones" it to the current directory. There is no "versus" here, they are two completely different operations. commit vs. push Commit records the changes to the local repository. Push basically takes a ref (a mapping to a sha-1 value that identifies a commit in the tree) and updates a ref in a remote repository. In essence, you are pushing your changes to the remote repository. Again, the thinking of a VCS person, not someone used to DVCSes. You have to know which commands work locally and which work with "the server" Only if you think in terms of centralized repositories. A DVCS is distributed. It's a completely different way of thinking. I find it superior in very many ways. Git has the advantage that it's MUCH better suited if some developers are not always connected to the master repository. The whole point of git is that you have your version, and you either pull from or push to different repositories and and when needed. The whole idea of centralization is not core to it at all.
- einhverfr 13y ago> Only if you think in terms of centralized repositories. A DVCS is distributed. It's a completely different way of thinking. I find it superior in very many ways. The benefits come at a cost though (I say this as someone who works with both). For many environments, a centralized VCS is all you need. Making it distributed just because that's a popular thing to do isn't necessarily always a good idea. It complicates workflows because now you have to have multiple version control systems which interact with eachother in far more complex ways. You don't want to go down that path if you don't need to. Now, despite the costs, there are many advantages to git. These include an ability to effectively treat your local repo as a master for a client. Also DVCS's scale to a larger number of developers more than traditional VCS's and git has advantages there too. BTW. one thing I find to be a killer feature of github is the fact that it offers you svn access to git repos, which can be really, really nice.
- chris_wot 13y agoWell, no. If you have a centralized git server (can be done), then you have the following workflow: 1. Make your changes, branch, do whatever you want to do. 2. Commit the changes to your repo. 3. Push your changes to the remote repo. 4. When you want to get other's changes, pull those changes. Heck, do a git pull -r if you want to rebase them. That is really not that complicated. However, you get the benefits of a local copy. So not what I'd really call totally distributed, but I can't see any downsides to this.
- einhverfr 13y ago> That is really not that complicated. It's still twice as many steps. Well, probably more if you count git add before every commit. Also a big problem for me is the necessity of a git add * before a commit, which effectively requires a lot of management of .gitignore so you don't get things like the Makefile.old getting committed. Keep in mind, all of this is process overhead, an opportunity to make mistakes, and effort (including tracking/fixing the mistakes) that could be spent programming. There are downsides. As I say, I do a fair bit with both and to be honest I am not that enthusiastic about git over svn. It's really good in some cases. However it isn't always better. Sometimes simpler tools are better.